Bug 1157856
Summary: | Request to change hostname logic handling for "static"/"none" interface configuration | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Bryan Totty <btotty> | |
Component: | initscripts | Assignee: | David Kaspar // Dee'Kej <deekej> | |
Status: | CLOSED ERRATA | QA Contact: | Jan Ščotka <jscotka> | |
Severity: | medium | Docs Contact: | Clayton Spicer <cspicer> | |
Priority: | medium | |||
Version: | 6.7 | CC: | ckozler, cww, deekej, jpopelka, jscotka, psklenar | |
Target Milestone: | rc | Keywords: | Patch | |
Target Release: | --- | |||
Hardware: | All | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | initscripts-9.03.55-1 | Doc Type: | Enhancement | |
Doc Text: |
The `NO_DHCP_HOSTNAME` option has been added
The `NO_DHCP_HOSTNAME` option can now be specified in the `/etc/sysconfig/network` configuration file. Previously, in certain situations it was not possible to prevent initialization scripts from obtaining the host name through DHCP, even when using a static configuration. With this update, if the `NO_DHCP_HOSTNAME` option is set to `yes`, `true`, or `1` in the `/etc/sysconfig/network` file, initialization scripts are prevented from obtaining the host name through DHCP.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1398672 (view as bug list) | Environment: | ||
Last Closed: | 2017-03-21 11:51:52 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: | 1172231, 1269194, 1356047, 1398672 |
Description
Bryan Totty
2014-10-27 21:15:48 UTC
Hmmm, I don't think that changing default behavior would be a good idea. Someone else could be using that and having regressions is much worse. I am still not sure what is not enough just to set HOSTNAME in sysconfig/network. But otherwise I would be open to some new option for sysconfig/network like DHCPHOSTNAME. I believe that any option that gives control back to the administrator of the system will be acceptable. We just don't want the hostname being taken control of when using a static configuration. Hi Lukáš Nykrýn - Bryan is exactly right. I am the original requestor and ultimately having a system assume dynamic behavior when not configured in such a manner is undesired. This can break upstream processes such as bootstrapping or other automated processes which can break if the system makes assumptions. An option such that DHCPHOSTNAME=yes/no or something of the similar that tells the system to set the local hostname would be ideal in that we could then set this flag in our template vs alternative routes of trying to manage it through sysctl.conf (eg: once deployment is complete then unset manual setting in sysctl). Thanks Hmm this needs a patch i dhclient and unfortunately we will not make it in 6.7, so lets postpone it to 6.8 What is the patch required in dhclient? we should not modify need_hostname function, because its behavior should be stable. So if we want to add some additional variable it should be also read directly by dhclient-script Adding maintainer of dhclient to CC. Hello Bryan and Charles, we were discussing possible options and we decided to introduce a new option 'NO_DHCP_HOSTNAME' for you that you could set in /etc/sysconfig/network file: https://github.com/fedora-sysv/initscripts/pull/39 We're open to discussion in case you see this not sufficent to fix your issues. Best regards, David 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-2017-0786.html |