Issue #7002
Streamed responses don't appear in the access_log of the pulpcore-content app
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
- Create an RPM Remote with policy=on_demand
- Sync a repository using that remote.
- Create a publication from the new repository version.
- Create a distribution associated with the publication.
- Request a non-metadata file from the base_url of the distribution
- Notice that the request is not logged
- Request the same file again.
- Notice that the request is logged this time.
I expect the request to appear in the logs every time.
Associated revisions
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)
History
#1
Updated by fao89 about 1 year ago
- Triaged changed from No to Yes
- Sprint set to Sprint 75
#6
Updated by gerrod 11 months ago
- Status changed from POST to MODIFIED
Applied in changeset pulpcore|9208b80a984433c4e058c1fb5d2875aac8a7e702.
#7
Updated by gerrod 11 months ago
Applied in changeset pulpcore|f0c6967b9abc02371ed1c9928bc19e99599dce5a.
#8
Updated by dkliban@redhat.com 10 months ago
- Sprint/Milestone set to 3.6.0
Please register to edit this issue
.
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