yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #42501
[Bug 1506503] Re: OVS agents periodically fail to start in fullstack
** Changed in: neutron
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1506503
Title:
OVS agents periodically fail to start in fullstack
Status in neutron:
Fix Released
Bug description:
Changeset [1] introduced a validation that the local_ip specified for
tunneling is actually used by one of the devices on the machine
running an OVS agent.
In Fullstack, multiple tests may run concurrently, which can cause a
race condition: suppose an ovs agent starts running as part of test A.
It retrieves the list of all devices on the host and starts a
sequential loop on them. In the mean time, some *other* fullstack test
(test B) completes and deletes the devices it created. The agent has
that deleted device in the list and when it will reach the device it
will find out it does not exist and crash.
[1]: https://review.openstack.org/#/c/154043/
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1506503/+subscriptions
References