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.
* Description of problem:
Anaconda will set the hostname of a system based on DNS. If no entires are found it will set it to localhost.
There is no way to stop this behaviour.
* Steps to Reproduce:
1. set hostname in kickstart with "network --hostname=<blah>"
2. boot installation with ip=dhcp and inst.ks=http://X.X.X.X/ks.cfg
3.
* Actual results:
NetworkManager will set the hostname based on DNS results and not the kickstart
Jun 21 14:28:10 test.net NetworkManager[1747]: <info> [1624285690.4197] policy: set-hostname: current hostname was changed outside NetworkManager: 'test.net'
Jun 21 14:28:10 test.net NetworkManager[1747]: <info> [1624285690.4198] policy: set-hostname: set hostname to 'localhost' (from address lookup)
* Expected results:
Preferably we should be able to either disable this feature of NetworkManager.
Or if a hostname is set to something other than localhost, NetworkManager should not overwrite that.
* Additional info:
This was discussed in Bug 1766944. Opening the request for these options.
https://bugzilla.redhat.com/show_bug.cgi?id=1766944#c20
This could be eventually done by installer boot option (something like inst.nm.hostname.only-from-default). As a global modification of installer environment this does not seem to belong to kickstart.
Also it would apply only to devices/connections configured by kickstart after switch root (NM activating connections in initramfs would be unaffected in this respect).