neutron: VirtualInterface isn't cleaned up before rescheduling during allocation failure
Bug #1603197 reported by
Matt Riedemann
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Matt Riedemann |
Bug Description
This is a follow-on to bug 1602357. That fixed the case that we delete the VirtualInterface objects in the nova db when deallocating networks for an instance or a single port.
But if we fail to allocate networking from the start, we also do a cleanup on the ports we've created and/or updated, but we aren't deleting the VIFs we've created, here:
That also needs to happen because we could do something like:
1. create/update port1, create vif1, ok
2. create/update port2, fails - we deallocate port1 and port2 but not vif1
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/342416
Review: https:/