Created attachment 917123 [details]
Puppet yaml for failing node
I'm trying to deploy an HA configuration using staypuft, and Puppet on the controllers is failing with:
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Local ip for ovs agent must be set when tunneling is enabled at /etc/puppet/environments/production/modules/neutron/manifests/agents/ovs.pp:31 on node 525400fef618.localdomain
I've attached the puppet yaml (/var/lib/puppet/yaml/node/<hostname>.yaml) for one of the failing nodes to this bz.
I'm still seeing this with:
OK, think I have an idea what this is, Scott is working on a fix.
So, the basic problem here is that the installer does not configure interfaces other than the provisioning interface, event those explicitly selected for use as the OVS tunnel interface.
This means that when the installer goes to find the ipaddress_<ifname> fact for the OVS tunnel interface it doesn't exist (because the interface was not up), and the install fails with the error described above.
The simplest fix would be to have the installer default all interfaces to use DHCP and to come up on boot.
Someone could still override this behavior in the kickstart template, but hopefully in many situations this would not be necessary and the interfaces would get configured automatically.
This was discussed some time ago and we agreed that for phase 1 we are OK with defaulting all eth devices to use DHCP, and allow static configurations on Staypuft Phase 2.
On almost every host I've ever looked at, OOB management cards do *not* show up in the OS. The consequences of not having the nics activated is worse than if we get an ip address on the OOB card (which it should have anyway, just not OS visible).
If we want to detect OOB cards and not activate those, please file a separate bug.
new bug for OOB is filed - https://bugzilla.redhat.com/show_bug.cgi?id=1129521
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.