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.
DescriptionLukáš Hellebrandt
2017-10-11 10:11:43 UTC
Description of problem:
In capsule-certs-generate, the parameter --capsule-fqdn has been changed to --foreman-proxy-fqdn. Why? In Satellite terminology, we use Capsule, not Foreman Proxy.
If we, for any reason, decide to keep the change, the documentation needs to reflect it; I know of these occurences:
4.6.1. Configuring Capsule Server with a Default Server Certificate , part 1
4.7.6.3. Create the Capsule Server’s Certificate Archive File, parts 2 and 4
Numbering taken from 6.2 Installation Guide: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.2/html/installation_guide/installing_capsule_server