Created attachment 1030555 [details]
instack network settings
Description of problem:
The dns_nameservers for the provisioning network on the undercloud is set to 192.168.122.1 within a baremetal environment which breaks name resolution on overcloud nodes.
Version-Release number of selected component (if applicable):
[stack@bldr16cc09 ~]$ rpm -qa | grep tripleo
Steps to Reproduce:
1. install undercloud
2. neutron net-list
3. neutron subnet-show <subnet_id>
dns_nameservers set to 192.168.122.1
We should be able to provide DNS servers in the instack.answers file so overcloud nodes get a valid DNS server via DHCP on the provisioning network.
I'm attaching my instack.answers file and out of network related settings.
Where should we set the dns server(s)? I don't see anything related in undercloud.conf but I might be missing something. Thanks
Marius, can you confirm your overcloud dns is not pointing to 192.168.122.1 anymore though? (but to the neutron managed dnsmasq running in the undercloud)
Confirmed, overcloud resolv.conf contains the ip address set on the dhcp namespace on the undercloud.
(In reply to Marius Cornea from comment #6)
> Where should we set the dns server(s)? I don't see anything related in
> undercloud.conf but I might be missing something. Thanks
you set the dns servers by running a neutron subnet-update command prior to deploying the overcloud. this is included in the documentation.
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.