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.
Description:
After completing satellite-change-hostname on satellite, It suggests following to be executed on capsule server but that leaves the "server_foreman_url" paramater with old value on capsule.
foreman-installer --foreman-proxy-content-parent-fqdn new-sat-hostname.example.com \
--foreman-proxy-foreman-base-url https://new-sat-hostname.example.com \
--foreman-proxy-trusted-hosts new-sat-hostname.example.com
Component [ Versions if applicable ]:
Sateliite 6.10 [ Latest Snap ]
How Reproducible:
Always
Steps to reproduce:
1. Install a satellite and capsule with hostnames set as satellite.example.com and capsule.example.com
2. Run : satellite-change-hostname on satellite:
# satellite-change-hostname new-sat-hostname.example.com -u admin -p XXXX -y
3. Observed the message printed at the end and execute the steps on capsule.example.com
4. Look for the availability of old satellite hostname in /etc/foreman-installer/scenarios.d/capsule-answers.yaml file of capsule.
Actual Results:
At step 3: It will suggest:
~~
foreman-installer --foreman-proxy-content-parent-fqdn new-sat-hostname.example.com \
--foreman-proxy-foreman-base-url https://new-sat-hostname.example.com \
--foreman-proxy-trusted-hosts new-sat-hostname.example.com
~~
At Step 4:
We will see old FQDN is set for server_foreman_url parameter:
# grep server_foreman_url /etc/foreman-installer/scenarios.d/capsule-answers.yaml
server_foreman_url: https://satellite.example.com
Expected Results:
1. At step3, it should suggest:
satellite-installer --foreman-proxy-content-parent-fqdn new-sat-hostname.example.com \
--foreman-proxy-foreman-base-url https://new-sat-hostname.example.com \
--foreman-proxy-trusted-hosts new-sat-hostname.example.com \
--puppet-server-foreman-url https://new-sat-hostname.example.com
2. At Step4 The output should show new FQDN:
# grep server_foreman_url /etc/foreman-installer/scenarios.d/capsule-answers.yaml
server_foreman_url: https://new-sat-hostname.example.com
Additional Notes:
NA
It seems we are missing this from documentation as well. So there also exact same change will be needed.
Let me know if I should file a separate DOC BZ for that.
Checked on Satellite 6.10 snap 23
the output suggestion of rename command reads:
foreman-installer --foreman-proxy-content-parent-fqdn new-hostname \
--foreman-proxy-foreman-base-url https://new-hostname \
--foreman-proxy-trusted-hosts new-hostname \
--puppet-server-foreman-url https://new-hostname
The downstream branding apparently didn't get applied (would expect satellite-installer)
Moreover, when running the command at the capsule, I get:
ERROR: Unrecognised option '--foreman-proxy-content-parent-fqdn'
Verified on Satellite 6.10.1, the suggested command is branded, contains --puppet-server-foreman-url, does not contain --foreman-proxy-content-parent-fqdn, and runs successfully on capsule
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Satellite 6.10.1 Async Bug Fix Update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2021:4737
Description: After completing satellite-change-hostname on satellite, It suggests following to be executed on capsule server but that leaves the "server_foreman_url" paramater with old value on capsule. foreman-installer --foreman-proxy-content-parent-fqdn new-sat-hostname.example.com \ --foreman-proxy-foreman-base-url https://new-sat-hostname.example.com \ --foreman-proxy-trusted-hosts new-sat-hostname.example.com Component [ Versions if applicable ]: Sateliite 6.10 [ Latest Snap ] How Reproducible: Always Steps to reproduce: 1. Install a satellite and capsule with hostnames set as satellite.example.com and capsule.example.com 2. Run : satellite-change-hostname on satellite: # satellite-change-hostname new-sat-hostname.example.com -u admin -p XXXX -y 3. Observed the message printed at the end and execute the steps on capsule.example.com 4. Look for the availability of old satellite hostname in /etc/foreman-installer/scenarios.d/capsule-answers.yaml file of capsule. Actual Results: At step 3: It will suggest: ~~ foreman-installer --foreman-proxy-content-parent-fqdn new-sat-hostname.example.com \ --foreman-proxy-foreman-base-url https://new-sat-hostname.example.com \ --foreman-proxy-trusted-hosts new-sat-hostname.example.com ~~ At Step 4: We will see old FQDN is set for server_foreman_url parameter: # grep server_foreman_url /etc/foreman-installer/scenarios.d/capsule-answers.yaml server_foreman_url: https://satellite.example.com Expected Results: 1. At step3, it should suggest: satellite-installer --foreman-proxy-content-parent-fqdn new-sat-hostname.example.com \ --foreman-proxy-foreman-base-url https://new-sat-hostname.example.com \ --foreman-proxy-trusted-hosts new-sat-hostname.example.com \ --puppet-server-foreman-url https://new-sat-hostname.example.com 2. At Step4 The output should show new FQDN: # grep server_foreman_url /etc/foreman-installer/scenarios.d/capsule-answers.yaml server_foreman_url: https://new-sat-hostname.example.com Additional Notes: NA