nova-manage network delete fails with QuantumManager
Bug #902175 reported by
Isaku Yamahata
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Brad Hall | ||
neutron |
Fix Released
|
High
|
Brad Hall | ||
quantum (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
With QuantumManager network driver and linux_net LinuxOVSInterfa
- create network
- create an instance and terminate
- then nova-manage network delete fails.
And the db state remains inconsistent state. It requires manual fix by issuing SQL.
The reason is
- LinuxOVSInterfa
- It creates gw-xxx and register the port to Quantum at the time first instance is created
- When deleting network, the gw-xxx reamins. So network deletion request to quantum fails
due to the interface gw-xxx is attached and busy.
The fix would be
- implement unplug and call unattach and delete the port request to quantum
- stop dnsmasq daemon
Changed in nova: | |
assignee: | nobody → Brad Hall (bgh) |
Changed in quantum: | |
importance: | Undecided → High |
status: | New → In Progress |
Changed in nova: | |
status: | New → In Progress |
Changed in quantum: | |
status: | In Progress → Fix Committed |
Changed in nova: | |
status: | In Progress → Fix Committed |
Changed in nova: | |
milestone: | none → essex-2 |
status: | Fix Committed → Fix Released |
Changed in quantum: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | essex-2 → 2012.1 |
Changed in quantum: | |
milestone: | essex-2 → 2012.1 |
Changed in quantum (Ubuntu): | |
status: | New → Fix Released |
To post a comment you must log in.
Hi Isaku!
Thanks for reporting this bugs, and for proposing a strategy for fixing it.
I'm not really up-to-date on the Quantum-nova integration, but I was wondering why we would need to stop dnsmasq. This might make sense with the VLAN manager, altough I think there is already code in place for destroying resources on the network node, including the dnsmasq instance, when a network is delete.
However, in FlatDHCP mode, if I'm not wrong the same dnsmasq instance is used for all networks (several IP addresses are configured on the bridge).