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.
Update the doc with the correct steps on how to update client certs post updating custom certs on the satellite as katello-ca-consumer package is deprecated
Hello,
Many thanks for bringing this to our awareness.
Updates about progress on the implementation of the fix will be shared in this ticket.
Thank you!
Product BZs are already raised by me earlier around the same topic:
2124052 – As usage of katello-ca-consumer rpm has been deprecated, the capsule-certs-generate command should suggest alternate approach during SSL cert installation\renewal
https://bugzilla.redhat.com/show_bug.cgi?id=2124052
2185634 – [RFE] Alternate method of katello-ca-cosumer to populate SSL certs on client systems
https://bugzilla.redhat.com/show_bug.cgi?id=2185634
Since we don't have any other options present yet, Can we do this on the client systems, instead of installing katello-ca-consumer rpm or it has some downsides ?
# curl http://<satellite-or-capsule-fqdn>/pub/katello-rhsm-consumer | bash
Even though, we have deprecated the katello-ca-consumer rpm package, the mentioned way (above PR) is not addressing the issue technically. Based on the conversation on the above PR, we have mutually agreed to have an optimal solution in the future to better address the issue/requirement.
Thank you for the feedback.