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:
When customer was following install guide to deploy custom certificates capsule was not working despite successful capsule-installer.
Customer found that
/etc/foreman-proxy/ssl_cert.pem
/etc/foreman-proxy/ssl_key.pem
have not been updated by the procedure and updated them manually, after that everything worked
Version-Release number of selected component (if applicable): Satellite 6.1.3
How reproducible:
Steps to Reproduce:
1. Set up Satellite and external Capsule and check it's working
2. Apply custom certificates on Satellite6 following install guide
3. Apply custom certificate on Capsule following install guide and
output of capsule-certs-generate
Actual results:
not all certificates on capsule got updated but
/etc/foreman-proxy/ssl_cert.pem
/etc/foreman-proxy/ssl_key.pem
had to be updated by hand
Expected results:
capsule-installer shall not show successful installation
Additional info:
according to the log files i could not find any hints why this failed
I think the issue could be here with updating the capsule with the new certs.
I believe for some reason the new certs from the newer version of the created pacakges inside the tar file, do not get installed.
Will check in more detail and update here.
NOTE: Setting up everything the first time itself using the custom certs, works completely fine.