Bug 2124052
Summary: | As usage of katello-ca-consumer rpm has been deprecated, the capsule-certs-generate command should suggest alternate approach during SSL cert installation\renewal | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Sayan Das <saydas> |
Component: | Installation | Assignee: | satellite6-bugs <satellite6-bugs> |
Status: | CLOSED MIGRATED | QA Contact: | Satellite QE Team <sat-qe-bz-list> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.12.0 | CC: | ahumbe, ehelms, jbhatia, wpinheir |
Target Milestone: | Unspecified | Keywords: | MigratedToJIRA |
Target Release: | Unused | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2024-06-06 12:30:32 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Sayan Das
2022-09-04 10:01:06 UTC
And whatever new method will be identified, that should be updated in https://access.redhat.com/documentation/en-us/red_hat_satellite/6.11/html-single/installing_satellite_server_in_a_connected_network_environment/index#deploying-a-custom-ssl-certificate-to-hosts_satellite as well. or else we are again suggesting to perform these steps on all clients of satellite\capsule after the SSL Cert update on satellite\capsule i.e. # yum localinstall \ http://satellite.example.com/pub/katello-ca-consumer-latest.noarch.rpm The same would be applicable for a scenario where we will update the SSL CA for Satellite itself and the same updated CA needs to be populated to the client systems as well. But right now, The only way we can do that is by re-registering the systems. We would need something much simpler or perhaps a mini version of SSL CA update snippet that can be executed in the same manner as global registration method. Converted comment 2 into a new RFE https://bugzilla.redhat.com/show_bug.cgi?id=2185634 Based on my discussion with Leos, converting BZ 2124052 into a bug. *** Bug 2253311 has been marked as a duplicate of this bug. *** This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |