Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2073124 - HTTP responses include incorrect ETag value
Summary: HTTP responses include incorrect ETag value
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: RH Cloud - Insights
Version: 6.10.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: 6.11.0
Assignee: Shimon Shtein
QA Contact: addubey
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-07 16:39 UTC by Link Dupont
Modified: 2023-05-19 09:46 UTC (History)
4 users (show)

Fixed In Version: rubygem-foreman_rh_cloud-5.0.34
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-07-05 14:35:12 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
python script comparing the two HTTP responses (702 bytes, text/x-python)
2022-04-07 16:39 UTC, Link Dupont 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github theforeman foreman_rh_cloud pull 716 0 None Merged Properly treat caching headers 2022-06-02 14:32:27 UTC
Red Hat Product Errata RHSA-2022:5498 0 None None None 2022-07-05 14:35:23 UTC

Description Link Dupont 2022-04-07 16:39:43 UTC 
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:
Comment 1 Shimon Shtein 2022-04-11 12:55:24 UTC 
Created a PR that should fix the issue
Comment 5 errata-xmlrpc 2022-07-05 14:35:12 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.