Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionJoniel Pasqualetto
2022-05-25 19:53:55 UTC
Description of problem:
When loading the list of Red Hat Repositories (Content -> Red Hat Repositories), Satellite won't follow redirects.
Version-Release number of selected component (if applicable):
How reproducible:
Always, when the cdn url sends a redirect
Steps to Reproduce:
1. Modify the CDN url to http://cdn.redhat.com (note the HTTP, not HTTPS)
2. Go to Content -> Red Hat Repositories. Try expanding any repository know to have multiple options to be enabled. Nothing will be loaded.
Actual results:
Redirects are not followed and users can't enable repositories.
Expected results:
http redirects to be followed.
Additional info:
Based on the discussion with the engineer from case 03426678, I am reopening this Bugzilla.
Since this was never really fixed in the product but worked around, I believe we need more investigation to be done here.
These are the questions raised by the case engineer to me :
A) Why 6.11 is working for the end-user but not 6.12 ? ( any specific change in katello is not allowing the workaround to do its job ?? )
B) Who is responsible for redirecting https://cdn.redhat.com to https://ru-by-exceptions.cdn.redhat.com ?
--> If it's RedHat, then what is the exact necessity of the same?
--> The RU-BY exceptions had ended quite some time back
C) Is there a product-level permanent fix we can suggest to the customer?
D) If C is false then What sort of data would be required from the customer to investigate this issue going forward and find out a viable solution ?
-- Sayan
JFYI, As the end-user was not experiencing the exact same issue as before but rather, it seems like manifest certs are not allowing access to the content hosted in ru-by cdn mirror, we decided to treat it as simple "403 forbidden" scenario, and go for a manifest refresh.
I have additionally requested them to refresh the pulp repos in Library env i.e. foreman-rake katello:refresh_pulp_repo_details LIFECYCLE_ENVIRONMENT=Library
Let's see if that results in any positive outcome ..