testenv nodes DHCP br-untagged from two DHCP servers

[Robert Collins]

the undercloud network address on br-ctlplane is dhcp allocated, but when that bridge dhcps it gets the tripleo-bm-test ip not the undercloud address (or the other, randomly), leading to not being accessible from the undercloud control plane, and being unable to update metadata(or not contact the broker/jenkins slaves)

we might be able to add an alias with a custom MAC for this, or possibly just register the IP with a custom mac and apply it ourselves.

is critical because when these drop-off the network, all tests fail.

ALSO - any reboot of the nodes will randomly have them DHCP from the wrong server, with no PXE boot flags. SO they will fail to boot.

[Dan Prince (dan-prince)]

I think this all one big bug. Lets just go with 1272969.

[Robert Collins (lifeless)]

(it's not one bug, because this isn't about incorrect ovs stuff this is about dhcping one interface from two servers :)

[Robert Collins (lifeless)]

One answer to this would be to kill dhclient after getting the network up. I kindof like this approach:)

[Derek Higgins (derekh)]

https://review.openstack.org/#/c/91333/

[Derek Higgins (derekh)]

Changing to high,
  fix in gerrit and not blocking anything, TE's can be rebuilt if if this causes a problem in any.

[Derek Higgins (derekh)]

Test env images rebuilt ages ago, closing