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.
To make the workaround public:
Steps to Reproduce:
1. Install a Satellite with 3rd party CA
2. Install a capsule without 3rd party CA certs
3.
Actual results:
Fails
Expected results:
for the capsule installer to succeed
Additional info:
The fix is very easy:
On the satellite:
# cat /etc/pki/katello/certs/katello-default-ca-stripped.crt >> /etc/foreman/proxy_ca.pem
Rerun the installer.
The documentation says to sign the capsule certs with the same CA as the Satellite. Since this is a oneoff I am marking this as WONTFIX and would suggest a KCS solution be made with https://bugzilla.redhat.com/show_bug.cgi?id=1483108#c3