Comment 14 for bug 1481889

Revision history for this message
Martin Falatic (martinfalatic) wrote : Re: pod-create fails ('NoneType' object has no attribute 'status')

Closing as "Cannot reproduce (anymore)".

After tearing down all test machines on that VLAN and reinstalling OS+devstack on one only, I'm not seeing the problem anymore (at least not yet). In my config, it is possible for machines to cross-talk - if two machines are listening for the same IP address they will see the other machine's network advertising it as well (even if it's not assigned to that VLAN). Furthermore this seems to persist even after unstacking due to components and configurations by devstack. Finally, there were evidently other intermediate bugs that prevented VMs from being properly removed, further complicating the situation. A combination of changes since the problem was first seen (which wasn't a problem before that) as well as the fact that the internal network (or configuration of openstack's network currently) is more promiscuous than expected seems to be the root causes. One should exercise caution with shared network environments and Openstack Liberty's Magnum (and in case of problems, watch for resources that nova, etc., should have removed but did not, as these can interfere with current processes).