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.
Tested on: 6.14 - Snap 8
Steps to verify:
1. Import a manifest.
2. Navigate to Subscription -> Manage Manifest
3. Swap to a Custom CDN, and use this link: https://ru-by-exceptions.cdn.redhat.com
4. Attempt to view Repositories
Expected Results:
You are able to see and enable repositories.
Actual Results:
Repositories appear, but upon clicking not all are available to enable. Some are though, I'm guessing this is the result of only certain packages being available on the given custom CDN.
Upon attempting to enable these repositories, you are met with this error:
SSL_connect returned=1 errno=0 state=error: certificate verify failed (self signed certificate in certificate chain)
I'm unclear if this is an expected error given the status of our testing satellite setups, so I'd like some more clarification.
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 (Important: Satellite 6.14 security and bug fix update), 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-2023:6818