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.

Document URL: 

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.4/html/installing_satellite_server_from_a_connected_network/performing_additional_configuration_on_satellite_server#validate_the_satellite_server_ssl_certificate

Section Number and Name: 

3.7.2. Validate the Satellite Server’s SSL Certificate


Describe the issue: 

Screen section "Example output of katello-certs-check" does not match current version of script.

Suggestions for improvement: 

Remove at least the sections "To use them inside a NEW $CAPSULE" and "To use them inside an EXISTING $CAPSULE" and turn those into procedures.

Or, remove it all, because minimalism, and replace with procedures.

Additional information: 

Can wait for 6.5, it not urgent.

This issue was fixed in BZ#1625255.

Feel free to reopen if you have further concerns.

*** This bug has been marked as a duplicate of bug 1625255 ***