Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira ( 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 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 "", 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 1995119 - satellite-change-hostname is missing to suggest modification of "server_foreman_url" value for capsule servers
Summary: satellite-change-hostname is missing to suggest modification of "server_forem...
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: satellite-change-hostname
Version: 6.10.0
Hardware: All
OS: All
Target Milestone: 6.10.1
Assignee: wclark
QA Contact: Peter Ondrejka
Depends On:
TreeView+ depends on / blocked
Reported: 2021-08-18 13:30 UTC by Sayan Das
Modified: 2021-11-18 14:38 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-11-18 14:38:46 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 33580 0 Normal Closed Hostname change script should suggest new --puppet-server-foreman-url 2021-10-20 14:28:39 UTC
Foreman Issue Tracker 33719 0 Normal Closed change hostname suggests dropped parameter foreman-proxy-content-parent-fqdn 2021-10-20 14:28:37 UTC
Red Hat Product Errata RHBA-2021:4737 0 None None None 2021-11-18 14:38:51 UTC

Description Sayan Das 2021-08-18 13:30:54 UTC

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 \
                                  --foreman-proxy-foreman-base-url \

Component [ Versions if applicable ]:

Sateliite 6.10 [ Latest Snap ]

How Reproducible:


Steps to reproduce:

1. Install a satellite and capsule with hostnames set as and

2. Run : satellite-change-hostname on satellite:

# satellite-change-hostname -u admin -p XXXX -y

3. Observed the message printed at the end and execute the steps on

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 \
                                  --foreman-proxy-foreman-base-url \

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 

Expected Results:

1. At step3, it should suggest:

  satellite-installer --foreman-proxy-content-parent-fqdn \
                                  --foreman-proxy-foreman-base-url \
                                  --foreman-proxy-trusted-hosts \

2. At Step4 The output should show new FQDN:

# grep server_foreman_url /etc/foreman-installer/scenarios.d/capsule-answers.yaml 

Additional Notes:


Comment 1 Sayan Das 2021-08-18 13:46:29 UTC
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.

Comment 2 wclark 2021-09-28 23:08:05 UTC
Pursuing an upstream first change instead of the original downstream-only approach

Attached issue

Upstream PR is at

Comment 3 wclark 2021-10-05 17:51:57 UTC
Changing status to POST as upstream change has been merged. (I am not sure why automation did not take care of it in this case)

Comment 4 Peter Ondrejka 2021-10-15 14:45:01 UTC
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'

Comment 8 Peter Ondrejka 2021-11-09 14:35:51 UTC
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

Comment 13 errata-xmlrpc 2021-11-18 14:38:46 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.