Bug 1414332

Summary:	hostnamectl does not update DHCP_HOSTNAME
Product:	Red Hat Enterprise Linux 7	Reporter:	Marko Myllynen <myllynen>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED WONTFIX	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.3	CC:	systemd-maint-list
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-01-15 07:30:11 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:

Description Marko Myllynen 2017-01-18 10:12:55 UTC

Description of problem:
When installing RHEL 7 with a kickstart file that has something like:

network --device eth0 --bootproto dhcp --onboot yes --hostname test.example.com

/etc/hostname will contain test.example.com and ifcfg-eth0 will have:

DHCP_HOSTNAME="test.example.com"

Later, when changing hostname with hostnamectl(1), /etc/hostname is updated but ifcfg-eth0 is left untouched, this is then propagating to /var/lib/NetworkManager/dhclient-eth0.conf and also sent to the DHCP server.

Running dracut -f / rebooting or such tricks won't help, one would need to manually know to update ifcfg-eth0 to have the hostname configured in /etc/hostname and the hostname sent to the DHCP server in sync.

Thanks.

Version-Release number of selected component (if applicable):
systemd-219-30.el7_3.6.x86_64
NetworkManager-1.4.0-14.el7_3.x86_64

Comment 2 Jan Synacek 2017-02-13 11:23:45 UTC

DHCP_HOSTNAME is an override in case you don't want to use the actual HOSTNAME. The hostnamectl cannot know what (and if) you want to use as an override and it doesn't know anything about the network settings.

The question is why the DHCP_HOSTNAME was written in the ifcfg file. Maybe it was because of the combination of --device and --hostname? Otherwise I don't see any value of setting it.

Comment 4 RHEL Program Management 2021-01-15 07:30:11 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.