Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.
Document URL:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/performing_a_standard_rhel_9_installation/assembly_customizing-your-installation_installing-rhel#proc_configuring-network-and-host-name_network-hostnamehttps://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/performing_an_advanced_rhel_9_installation/kickstart-commands-and-options-reference_installing-rhel-as-an-experienced-user#network_kickstart-commands-for-network-configuration
Section Number and Name:
4.1.3.4.1. Configuring network and host name
B.4.1. network (optional)
Describe the issue:
The latter document states that FQDN should "always" be used if not using DHCP but provides no rationale for this guideline. Some major software products like SAP are known to require short name to be used in /etc/hostname so using FQDN "always" is not always possible. But provisioning some Red Hat components such as RH IdM will update /etc/hostname to contain FQDN if short name was used earlier.
Suggestions for improvement:
There is no one right or wrong answer whether /etc/hostname should contain short name or FQDN. However, we should ensure our documentation is consistent and in this particular case perhaps explain that the right answer depends on the situation.
I think the note in the first documented could be adjusted slightly (my proposal below) and the copied to the second document.
-----
The host name can be either a fully-qualified domain name (FQDN) in the format hostname.domainname, or a short host name with no domain name.
Many networks have a Dynamic Host Configuration Protocol (DHCP) service that automatically supplies connected systems with a domain name. To allow the DHCP service to assign the domain name to this machine, specify only the short host name.
When using static IP and host name configuration it depends on the planned system use case whether short name or FQDN should be used. Red Hat Identity Management configures FQDN during provisioning but some 3rd party software products may require short name to be used. In either case it is probably a good idea to add an entry for the host in /etc/hosts in the format "IP FQDN short-alias" to ensure availability of both forms in all situations.
The value localhost means that no specific static host name for the target system is configured, and the actual host name of the installed system is configured during the processing of the network configuration, for example, by NetworkManager using DHCP or DNS.
Host names can only contain alpha-numeric characters and - or .. Host names cannot start or end with - and .. In order to be compliant with DNS, each component of a FQDN should be no longer than 63 characters and the FQDN total length, including dots, should not exceed 255 characters.