Bug 2182649
| Summary: | [DDF] DOMAIN change of a satellite or capsule should be considered for satellite-change-hostname as well | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Direct Docs Feedback <ddf-bot> |
| Component: | satellite-change-hostname | Assignee: | Aneta Šteflová Petrová <apetrova> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Satellite QE Team <sat-qe-bz-list> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.12.0 | CC: | ehelms, lstejska, mjivraja, saydas |
| Target Milestone: | Unspecified | Keywords: | Documentation, Triaged |
| Target Release: | Unused | Flags: | mdolezel:
needinfo?
(mjivraja) |
| 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: | 2023-07-03 16:39:53 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Direct Docs Feedback
2023-03-29 08:19:57 UTC
We have seen many support cases where end users wanted to know what they need to do if the hostname of the system remains the same but the DNS domain names require a change. FQDN = Hostname + DNS Domain Name Where satellite\capsule is very sensitive about FQDN and satellite-change-hostname targets changing the FQDN ( as hostname ) of the system. In "13.1. Renaming Satellite Server" , The first point of "Prerequisites" section sort of hints to the same but perhaps we would need to mention somewhere that, If hostname of the satellite\capsule remains the same but the domain name is required to be updated, Then the end-users should consider as hostname change and use satellite-change-hostname to do so. CC'ing Malhar and Leos Pull request available here: https://github.com/theforeman/foreman-documentation/pull/2231 Hi Sayan, I'd like to clarify one thing: Is updating the hostname in this situation a recommendation (SHOULD) or a requirement (MUST)? See also the discussion in the PR: https://github.com/theforeman/foreman-documentation/pull/2231#discussion_r1241722235 Hello, Apologies for the delay in response. I was on leave and hence could not reply earlier. I have shared my direct feedback on https://github.com/theforeman/foreman-documentation/pull/2231#discussion_r1247474871. To answer your question, Satellite understands FQDN FQDN = Hostname + DNS Domain Name If either of the `Hostname` or `DNS Domain Name` is being changed by hand but the end-user did not consider using satellite-change-hostname instead, That will cause immediate operational challenges for satellite or the external smart-proxy from both Network as well as SSL point of view. If the CU is using SSL certificates with one or more wildcard domains, that's a different story but such implementation is very rare to see in production environments. So for every other scenario, The end-user cannot just change the hostname or DNS domain name and expect that satellite\capsule will continue to work normally. They need to consider satellite-change-hostname and plan the activity accordingly. -- Sayan The update is now available on the Customer Portal: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.12/html-single/administering_red_hat_satellite/index#Renaming_satellite_Server_or_capsule_admin |