Bug 1070253

Summary: anaconda: using FQDN hostname with DHCP/DDNS does not work anymore
Product: Red Hat Enterprise Linux 6 Reporter: Andreas Luik <andreas.luik>
Component: initscriptsAssignee: Lukáš Nykrýn <lnykryn>
Status: CLOSED ERRATA QA Contact: Jan Ščotka <jscotka>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.5CC: andreas.luik, jscotka, psklenar, sbueno
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Unspecified   
Whiteboard:
Fixed In Version: initscripts-9.03.50-1.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-11 01:04:53 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:
Bug Depends On:    
Bug Blocks: 1270825    

Description Andreas Luik 2014-02-26 13:44:11 UTC 
Description of problem:

In RHEL 6.5, anaconda's behaviour changed w.r.t. to usage of network configuration with --bootproto=dhcp and --hostname, please see
https://bugzilla.redhat.com/show_bug.cgi?id=917815

With this change, the ifcfg-NIC config file contains the (new) line

DHCP_HOSTNAME="myhostname"

If a FQDN is used with the kickstart config directive
network --bootproto=dhcp --hostname=myhostname.example.com
this results in

DHCP_HOSTNAME="myhostname.example.com"



Unfortunately, the following bug is not yet fixed in RHEL 6.5:
Bug 697877 - dhclient sends FQDN as a host name in DHCP request

This results in the following dhclient call on the system:

/sbin/dhclient -H myhostname.example.com ...

which is wrong: the -F option must be used to specify a FQDN.

The result is that registration of the hostname with ddns on our DHCP server did work with RHEL 6.4 and before (because the -H option was not passed at all),
but now it fails.

Version-Release number of selected component (if applicable):

anaconda-13.21.215-1.el6
initscripts-9.03.40-2.el6


How reproducible: always


Steps to Reproduce:
1. run kickstart installation with "network --bootproto=dhcp --hostname=myhostname.example.com"
2. perform installation
3. observe that the (FQDN-) hostname cannot be registered at the DHCP server

Actual results:

dhclient tries to register FQDN with -H


Expected results:

dhclient registers FQDN with -F
or dhclient registers hostname without domain with -H



Additional info:

Probably the best fix would be in initscripts, as described in Bug 697877 (for Fedora), which would need a backport to RHEL 6.x.
Comment 2 Samantha N. Bueno 2015-07-17 17:05:17 UTC 
(In reply to Andreas Luik from comment #0)
> 
> Additional info:
> 
> Probably the best fix would be in initscripts, as described in Bug 697877
> (for Fedora), which would need a backport to RHEL 6.x.

Changing the component then.
Comment 3 Lukáš Nykrýn 2015-07-20 08:04:27 UTC 
Looks sane for backport in 6.8.
Comment 4 Lukáš Nykrýn 2015-12-15 13:35:48 UTC 
https://git.fedorahosted.org/cgit/initscripts.git/commit/?id=cd475bf
Comment 8 errata-xmlrpc 2016-05-11 01:04:53 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-0951.html