Bug 1172377

Summary:	After rebooting styapuft machine ,the /etc/resolv.conf doesn't have the staypuft server in the nameservers list.
Product:	Red Hat OpenStack	Reporter:	Leonid Natapov <lnatapov>
Component:	rhel-osp-installer	Assignee:	Mike Burns <mburns>
Status:	CLOSED EOL	QA Contact:	Omri Hochman <ohochman>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	6.0 (Juno)	CC:	juwu, mburns, oblaut, rhos-maint, srevivo
Target Milestone:	---	Keywords:	ZStream
Target Release:	Installer
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Known Issue
Doc Text:	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'.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-09-29 13:23:35 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 Leonid Natapov 2014-12-09 23:26:34 UTC

After rebooting styapuft machine ,the /etcresolv.conf doesn't have the staypuft server in the nameservers list. As a workaround I set DNSPEER=NO in the ifcfg files. If DNSPEER=YES after rebooting staypuft machine it takes nameservers provided by dhcp and removes staypuft server from the list.


Expected results:
staypuft server should be the top nameserver in the list

rhel-osp-installer-0.5.2-1.el7ost.noarch
openstack-puppet-modules-2014.2.6-1.el7ost.noarch
openstack-foreman-installer-3.0.5-1.el7ost.noarch
ruby193-rubygem-foreman_openstack_simplify-0.0.6-8.el7ost.noarch
rhel-osp-installer-client-0.5.2-1.el7ost.noarch

Comment 4 Jaromir Coufal 2016-09-29 13:23:35 UTC

Closing list of bugs for RHEL OSP Installer since its support cycle has already ended [0]. If there is some bug closed by mistake, feel free to re-open.

For new deployments, please, use RHOSP director (starting with version 7).

-- Jaromir Coufal
-- Sr. Product Manager
-- Red Hat OpenStack Platform

[0] https://access.redhat.com/support/policy/updates/openstack/platform