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.
DescriptionSteffen Froemer
2023-08-31 10:21:36 UTC
Document URL: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.11/html/administering_red_hat_satellite/renewing-the-custom-ssl-certificate_admin#Renewing_a_Custom_SSL_Certificate_on_capsule_admin
Section Number and Name: 13.2. Renewing a Custom SSL certificate on Capsule Server
Describe the issue:
On part 5, deploying the certificate, it's suggested to run following command:
```
# satellite-installer --scenario capsule \
--foreman-proxy-content-parent-fqdn "satellite.example.com" \
--foreman-proxy-register-in-foreman "true" \
--foreman-proxy-foreman-base-url \ "https://satellite.example.com"
--foreman-proxy-content-certs-tar "/root/My_Certificates/capsule.example.com-certs.tar" \
--certs-update-server
```
This output differs from the output the capsule-certs-generate command from section '2.' is providing.
Most problematic one, the argument '--foreman-proxy-content-parent-fqdn' does not exist in satellite-installer
Suggestions for improvement:
Remove the non-existing argument from command section
Additional information:
Double-checked on Satellite-6.11 through 6.13.