ovs-plugin-agent died when I delete vm
Bug #1050504 reported by
yong sheng gong
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Critical
|
dan wendlandt |
Bug Description
It is not easy to reproduce, but it is because I delete the vm, which leads to a interface deleted. If at this time the agent runs this command:
sudo ovs-vsctl --timeout=2 get Interface tap216a1c49-a6 external_ids
It will die.
Changed in quantum: | |
importance: | Undecided → Critical |
Changed in quantum: | |
status: | In Progress → Confirmed |
status: | Confirmed → In Progress |
tags: | removed: folsom-rc-potential |
no longer affects: | quantum/folsom |
Changed in quantum: | |
milestone: | folsom-rc2 → 2012.2 |
To post a comment you must log in.
Do you reckon it is a race condition as the interface is removed from the switch - we fetch the iface in the daemon_loop but then in the meanwhile it's deleted.
I don't think a lock on ovs while the iteration is in progress will be feasibible, but perhaps we can just double check for the existence of the interface. We found a similar bug in nova ages ago.