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.
Description of problem:
If we have a proxy set in Administer -> Settings -> General -> 'HTTP(S) proxy' then capsule installation/upgrade fails because Satellite is not able to connect to capsule through proxy. In this scenario, the solution is to either remove the proxy or add the capsule in 'HTTP(S) proxy except hosts' list.
Version-Release number of selected component (if applicable):
Satellite 6.x
How reproducible:
Always
Steps to Reproduce:
1. Set the proxy in Administer -> Settings -> General -> 'HTTP(S) proxy'
2. Proxy should not be configured for internal routing
3. Try installing or upgrade the existing capsule.
Actual results:
Installation or upgrade fails.
Expected results:
We should add the capsule FQDN in 'HTTP(S) proxy except hosts' automatically at the time of certificate generation on the Satellite or in some other way to prevent such issues.
Additional info:
Verified in 6.12.0 snap 8:
1) Using a Satellite with HTTP proxy set, the Capsule installation succeeded without any issues.
2) Using setup from 1) there was no regression observed in current coverage for Capsule and Capsule-Content components.
3) Using a 6.11.2 Satellite with HTTP proxy set and Capsule installed (and removed from the proxy except list) the Satellite upgrade succeeded without any issues and the N-1 Capsule was operational.
4) Using setup from 3) the Capsule upgrade succeeded without any issues and the Capsule remained operational.
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.12 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:8506