Bug 2073124
| Summary: | HTTP responses include incorrect ETag value | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Link Dupont <link> | ||||
| Component: | RH Cloud - Insights | Assignee: | Shimon Shtein <sshtein> | ||||
| Status: | CLOSED ERRATA | QA Contact: | addubey | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 6.10.0 | CC: | ahumbe, aruzicka, ehelms, jpathan | ||||
| Target Milestone: | 6.11.0 | Keywords: | Triaged | ||||
| Target Release: | Unused | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | rubygem-foreman_rh_cloud-5.0.34 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2022-07-05 14:35:12 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Created a PR that should fix the issue Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: Satellite 6.11 Release), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:5498 |
Created attachment 1871363 [details] python script comparing the two HTTP responses Description of problem: When a managed insights-client makes an HTTP request to fetch a new insights-core.egg, it includes the If-None-Match header with a value. The response it receives from the Satellite server is HTTP status code 304, including an ETag header with a value identical to what the client sent in the request. When I send a request directly to cert-api.access.redhat.com, it responds with HTTP status code 200, including an ETag header with a different value. Version-Release number of selected component (if applicable): insights-client-3.1.7 insights-core-3.0.268 How reproducible: always Steps to Reproduce: 1. Run the attached Python script on a host managed by Satellite Actual results: The HTTP request proxy to cert-api.access.redhat.com responds with 304 and includes an ETag header with the value already cached by the client. Expected results: The HTTP request proxy to cert-api.access.redhat.com should respond with 200 and include an ETag header with the value from cert-api.access.redhat.com. Additional info: