Bug 2182649 - [DDF] DOMAIN change of a satellite or capsule should be considered for satellite-change-hostname as well [NEEDINFO]
Summary: [DDF] DOMAIN change of a satellite or capsule should be considered for satell...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: satellite-change-hostname
Version: 6.12.0
Hardware: All
OS: All
high
high
Target Milestone: Unspecified
Assignee: Aneta Šteflová Petrová
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-29 08:19 UTC by Direct Docs Feedback
Modified: 2023-07-03 16:39 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-03 16:39:53 UTC
Target Upstream Version:
Embargoed:
mdolezel: needinfo? (mjivraja)


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-16814 0 None None None 2023-03-29 08:22:15 UTC

Description Direct Docs Feedback 2023-03-29 08:19:57 UTC
DOMAIN change of a satellite or capsule should be considered for satellite-change-hostname as well

Reported by: rhn-support-saydas

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.12/html/administering_red_hat_satellite/renaming_server_or_smart_proxy_admin#annotations:98401f07-33cc-42b4-9941-54b09432f53a

Comment 1 Sayan Das 2023-03-29 08:24:16 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

Comment 3 Aneta Šteflová Petrová 2023-06-14 09:02:50 UTC
Pull request available here: https://github.com/theforeman/foreman-documentation/pull/2231

Comment 4 Aneta Šteflová Petrová 2023-06-29 09:32:30 UTC
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

Comment 5 Sayan Das 2023-06-30 06:17:10 UTC
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

Comment 6 Aneta Šteflová Petrová 2023-07-03 15:57:00 UTC
PR merged: https://github.com/theforeman/foreman-documentation/pull/2231#issuecomment-1618417157


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