Project

Profile

Help

Issue #7002

closed

Streamed responses don't appear in the access_log of the pulpcore-content app

Added by dkliban@redhat.com almost 4 years ago. Updated over 3 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 77
Quarter:

Description

  1. Create an RPM Remote with policy=on_demand
  2. Sync a repository using that remote.
  3. Create a publication from the new repository version.
  4. Create a distribution associated with the publication.
  5. Request a non-metadata file from the base_url of the distribution
  6. Notice that the request is not logged
  7. Request the same file again.
  8. Notice that the request is logged this time.

I expect the request to appear in the logs every time.

Actions #1

Updated by fao89 almost 4 years ago

  • Triaged changed from No to Yes
  • Sprint set to Sprint 75
Actions #2

Updated by rchan almost 4 years ago

  • Sprint changed from Sprint 75 to Sprint 76
Actions #3

Updated by rchan over 3 years ago

  • Sprint changed from Sprint 76 to Sprint 77
Actions #4

Updated by gerrod over 3 years ago

  • Assignee set to gerrod
Actions #5

Updated by pulpbot over 3 years ago

  • Status changed from NEW to POST

Added by gerrod over 3 years ago

Revision 9208b80a | View on GitHub

Streamed responses are properly returned to handler to be logged

When a request for content that was on_demand occured for the first time, no logs where present due to the response not properly being return to the content handler, despite the response actually occuring.

fixes #7002 https://pulp.plan.io/issues/7002

Actions #6

Updated by gerrod over 3 years ago

  • Status changed from POST to MODIFIED

Added by gerrod over 3 years ago

Revision f0c6967b | View on GitHub

Streamed responses are properly returned to handler to be logged

When a request for content that was on_demand occured for the first time, no logs where present due to the response not properly being return to the content handler, despite the response actually occuring.

fixes #7002 https://pulp.plan.io/issues/7002

(cherry picked from commit 9208b80a984433c4e058c1fb5d2875aac8a7e702)

Actions #8

Updated by dkliban@redhat.com over 3 years ago

  • Sprint/Milestone set to 3.6.0
Actions #9

Updated by pulpbot over 3 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Also available in: Atom PDF