Public bug reported: 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: https://github.com/openstack/nova/blob/92a388a1e34559b2ce69d31fdef996ff029495a6/nova/network/neutronv2/api.py#L847 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 ** Affects: nova Importance: High Assignee: Matt Riedemann (mriedem) Status: Triaged ** Tags: neutron -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1603197 Title: neutron: VirtualInterface isn't cleaned up before rescheduling during allocation failure Status in OpenStack Compute (nova): Triaged 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: https://github.com/openstack/nova/blob/92a388a1e34559b2ce69d31fdef996ff029495a6/nova/network/neutronv2/api.py#L847 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 manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1603197/+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
