Bug 1995119
| Summary: | satellite-change-hostname is missing to suggest modification of "server_foreman_url" value for capsule servers | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Sayan Das <saydas> |
| Component: | satellite-change-hostname | Assignee: | wclark |
| Status: | CLOSED ERRATA | QA Contact: | Peter Ondrejka <pondrejk> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.10.0 | CC: | ahumbe, ehelms, myarboro, pcreech, wclark, zhunting |
| Target Milestone: | 6.10.1 | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-11-18 14:38:46 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
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. Pursuing an upstream first change instead of the original downstream-only approach Attached issue https://projects.theforeman.org/issues/33580 Upstream PR is at https://github.com/theforeman/foreman-packaging/pull/7140 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) 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