Back to bug 1172377

Who When What Removed Added
Leonid Natapov 2014-12-09 23:26:50 UTC CC oblaut
Leonid Natapov 2014-12-09 23:28:20 UTC Summary After rebooting styapuft machine ,the /etcresolv.conf doesn't have the staypuft server in the nameservers list. After rebooting styapuft machine ,the /etc/resolv.conf doesn't have the staypuft server in the nameservers list.
RHEL Program Management 2014-12-09 23:36:37 UTC Target Release --- 6.0
RHEL Program Management 2014-12-10 00:05:42 UTC Target Release 6.0 Installer
Mike Burns 2014-12-10 22:20:46 UTC CC mburns
Doc Text Cause: Multiple active nics on the RHEL-OSP Installer machine using DHCP with PEERDNS either not set or set to Yes

Consequence: During boot, these nics may "fight" over resolv.conf settings. This may lead to a missing nameserver entry for the Installer host meaning deployments will fail

Workaround (if any): Make sure all nics other than the one where DHCP is running have peerdns=no

Result: only the nic running dhcp is used to determine the contents of resolv.conf meaning the right entries for deployments will be there.
Doc Type Bug Fix Known Issue
Julie 2015-01-19 06:27:22 UTC CC juwu
Doc Text Cause: Multiple active nics on the RHEL-OSP Installer machine using DHCP with PEERDNS either not set or set to Yes

Consequence: During boot, these nics may "fight" over resolv.conf settings. This may lead to a missing nameserver entry for the Installer host meaning deployments will fail

Workaround (if any): Make sure all nics other than the one where DHCP is running have peerdns=no

Result: only the nic running dhcp is used to determine the contents of resolv.conf meaning the right entries for deployments will be there.
On a Red Hat Enterprise Linux OpenStack Platform Installer host, when DHCP is used and there are multiple active NICs, if the PEERDNS parameter is not set or set to 'yes', the /etc/resolv.conf setting may be overwritten during boot time and result in incorrect nameserver entries. To avoid this issue, make sure all NICs other than the one where DHCP is running have PEERDNS set to 'no'.
RHEL Program Management 2015-02-09 20:46:51 UTC Keywords ZStream
John Skeoch 2016-04-18 07:19:23 UTC CC yeylon srevivo
Jaromir Coufal 2016-09-29 13:23:35 UTC Status NEW CLOSED
Resolution --- EOL
Last Closed 2016-09-29 09:23:35 UTC

Back to bug 1172377