Description of problem: when deploying with the br-ex provisioning enabled, the puppet on the neutron node failed to resolve. after adding the staypuft server address to resolve.conf, things got fixed. My guess it is because the dhclient replaced the resolv.conf after adding the eth* to the bridge. There was a line: ; generated by /usr/sbin/dhclient-script in the resolv.conf Version-Release number of selected component (if applicable): rhel-osp-installer-0.1.6-4.el6ost.noarch How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: Warning: Unable to fetch my node definition, but the agent run will continue: Warning: getaddrinfo: Name or service not known Info: Retrieving plugin Error: /File[/var/lib/puppet/lib]: Failed to generate additional resources using 'eval_generate': getaddrinfo: Name or service not known Error: /File[/var/lib/puppet/lib]: Could not evaluate: Could not retrieve file metadata for puppet://staypuft.example.com/plugins: getaddrinfo: Name or service not known Wrapped exception: getaddrinfo: Name or service not known Error: Could not retrieve local facts: no address for neutron.example.com Error: Failed to apply catalog: Could not retrieve local facts: no address for neutron.example.com Error: Could not send report: getaddrinfo: Name or service not known
This issue showed up in bug 1124027 and was fixed in openstack-puppet-modules. the PEERDNS option was not copied to br-ex when it was created. *** This bug has been marked as a duplicate of bug 1124027 ***