Bug 1177164 - The staypuft server isn't listed as the first nameserver
Summary: The staypuft server isn't listed as the first nameserver
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhel-osp-installer
Version: 6.0 (Juno)
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: Installer
Assignee: Mike Burns
QA Contact: Omri Hochman
URL:
Whiteboard:
Depends On:
Blocks: 1177026
TreeView+ depends on / blocked
 
Reported: 2014-12-24 16:41 UTC by Leonid Natapov
Modified: 2015-09-24 16:55 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-24 16:55:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
/var/log (560.44 KB, application/octet-stream)
2014-12-24 16:41 UTC, Leonid Natapov
no flags Details

Description Leonid Natapov 2014-12-24 16:41:06 UTC
Created attachment 972796 [details]
/var/log

The staypuft server isn't listed as the first nameserver if provisioning IP was configured by rhel-osp-installer.

User can configure PXE IP/netmask before running rhel-osp-installer or set the PXE IP and metmask while running rhel-osp-installer.

If it's done while runnung rhel-osp-installer staypuft server isn't listed as first nameserver. As a result puppet doesn't run automatically.

Attached /var/log/messages directory.

Comment 2 Leonid Natapov 2015-01-19 10:43:19 UTC
rhel-osp-installer configures nameserver in resolv.conf file
when user defines provisioning interface while running rhel-osp-installer, staypuft nameserver may be not the first one because it depends on what interface comes up first when rhel-osp-installer restarts the network.

If provisioning interface comes up first - everything is ok.
If provisioning interface doesn't come up first,the w/a is to define provisioning interface prior running rhel-osp-installer.

Comment 3 Mike Burns 2015-01-19 13:32:53 UTC
The real fix for this is to set PEERDNS=no on all non-provisioning nics.  That will cause the right nameserver to be configured.  

I would argue that this is really a doc or release note only issue and not a blocker.

Comment 4 Leonid Natapov 2015-01-27 13:45:59 UTC
 I am facing this issue on my staypuft machine over and over again. it's a race that happens only on my machine, it should be in release notes with a suggested work around.

Comment 7 Mike Burns 2015-09-24 16:55:55 UTC
pretty sure this is a duplicate, and currentrelease


Note You need to log in before you can comment on or make changes to this bug.