This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 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
Summary: As usage of katello-ca-consumer rpm has been deprecated, the capsule-certs-ge...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.12.0
Hardware: All
OS: All
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
: 2253311 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-04 10:01 UTC by Sayan Das
Modified: 2024-10-05 04:25 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 12:30:32 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-19781 0 None Migrated None 2024-06-06 12:30:31 UTC

Description Sayan Das 2022-09-04 10:01:06 UTC 
Description of problem:

The usage of the katello-ca-consumer rpm has been deprecated and even removed from the Global registration workflow but when it comes to installing or renewing SSL certs of the external capsule, we will need to use the "capsule-certs-generate" command and it will suggest the installation of katello-ca-consumer rpm as well.


Version-Release number of selected component (if applicable):

Satellite 6.12 [ and all other versions ]


How reproducible:

Always


Steps to Reproduce:
1. Install a Satellite with Custom certs.
2. Proceed preparing certs and cert tar bundle for external capsule installation  
   

Actual results:

The katello-certs-check suggests using "capsule-certs-generate" and capsule-certs-generate suggests doing this:

###########
Preparing installation Done                                              
  Success!

  To finish the installation, follow these steps:

  If you do not have the Capsule registered to the Satellite instance, then please do the following:

  1. yum -y localinstall http://<sat fqdn>/pub/katello-ca-consumer-latest.noarch.rpm
  2. subscription-manager register --org "RedHat"
#############

In the case of an existing capsule, we don't even need to do step 2 but step 1 is good enough to update the CA for Capsules RHSM.


Expected results:


Provide an alternate option of :

~~
yum -y localinstall http://<sat fqdn>/pub/katello-ca-consumer-latest.noarch.rpm
~~

when doing SSL cert installation or Update for an external capsule


Additional info:


NA
Comment 1 Sayan Das 2022-09-04 10:06:37 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
Comment 2 Sayan Das 2023-03-20 09:21:34 UTC 
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.
Comment 3 Sayan Das 2023-04-10 17:05:57 UTC 
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.
Comment 5 Eric Helms 2023-12-14 16:26:47 UTC 
*** Bug 2253311 has been marked as a duplicate of this bug. ***
Comment 6 Eric Helms 2024-06-06 12:30:32 UTC 
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.
Comment 7 Red Hat Bugzilla 2024-10-05 04:25:26 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Note You need to log in before you can comment on or make changes to this bug.