I think this can be fixed by adding an upstart pre-start rule similar to
the one used in neutron-*-agent.upstart e.g.
pre-start script
# Check to see if openvswitch plugin in use by checking
# status of cleanup upstart configuration
if status neutron-ovs-cleanup; then
start wait-for-state WAIT_FOR=neutron-ovs-cleanup WAIT_STATE=running
WAITER=nova-compute
fi
end script
** Changed in: neutron
Assignee: (unassigned) => Edward Hope-Morley (hopem)
** Project changed: neutron => nova (Ubuntu)
** Changed in: nova (Ubuntu)
Assignee: Edward Hope-Morley (hopem) => (unassigned)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1420572
Title:
race between neutron-ovs-cleanup and nova-compute
Status in nova package in Ubuntu:
In Progress
Bug description:
There is a race when both neutron-ovs-cleanup and nova-compute trying
to do operations on the qvb*** and qvo*** devices. Below is a scenario
I recently met,
1. nova-compute was started and creating the veth_pair for VM
instances running on the host -
https://github.com/openstack/nova/blob/stable/icehouse/nova/network/linux_net.py#L1298
2. neutron-ovs-cleanup was kicked off and deleted all the ports.
3. when nova-compute tried to set the MTU at
https://github.com/openstack/nova/blob/stable/icehouse/nova/network/linux_net.py#L1280
, Stderr: u'Cannot find device "qvo***"\n' was reported. Because the
device that was just created was deleted again by neutron-ovs-cleanup.
As they both operate on the same resources, there needs a way to
synchronize the operations the two processes do on those resources.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1420572/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
