yahoo-eng-team team mailing list archive

[melanie witt <1617291@xxxxxxxxxxxxxxxxxx>]

*** This bug is a duplicate of bug 1639230 ***
    https://bugs.launchpad.net/bugs/1639230

** This bug is no longer a duplicate of bug 1609526
   Nova creates duplicate Neutron ports on instance reschedule
** This bug has been marked a duplicate of bug 1639230
   reschedule fails with ip already allocated error

-- 
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/1617291

Title:
  Nova creates duplicate Neutron ports on instance reschedule

Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  Neutron network driver in Nova creates new port unless port_id is
  specified.  If instance is rescheduled for some reason, these ports
  should either be deleted or re-used on next try.  Reuse doesn't happen
  because Neutron driver in Nova creates new port unless port_id is
  specified.  New port is then created and instance gets multiple ports
  (one for each reschedule attempt) while only one is "correct".

  This happens because on reschedule network cleanup only happens if
  virt driver tells to deallocate_networks_on_reschedule (which is only
  true for Ironic driver).

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1617291/+subscriptions