I'm going to remove 'nova' from this since we can track the nova issue
with bug 1597596. The powervm driver out of tree has fixed this
** No longer affects: nova
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
libvirt driver doesn't cleanup the tap interface on vm re-schedule
Status in nova-powervm:
Here when you use libvirt driver with tap interfaces, it creates a tap
interface on the host but doesn't clean up the interface and leaves
in-tact and creates another same named interface on the new host.
In _do_build_and_run_instance when RescheduledException is called,
manager checks if the network port needs to be de-allocated for a
different host or not using deallocate_networks_on_reschedule() which
is hard coded to return False. If this is changed to return true or
set via conf file configuration to allow being changed for specific
mech drivers in neutron then it would be helpful to not only clean up
the tap interface properly but also also mech drivers in neutron to
re-create new ports on new host instead of shifting and re-using same
ports which fails.
tested on master and stable/liberty and fails in both cases, so may
need back porting.
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp