yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: nova
       Status: Fix Committed => Fix Released

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

Title:
  Instance delete should fail in neutron.delete_port() fails

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  Currently neutronv2 deallocate_for_instance() will put the instance
  into an error state if neutron.list_ports() fails, but continue with
  the delete if the subsequent neutron.delete_port() fails - leaving
  ports behind in Neutron in a way that is not obvious to the user.

  It would be cleaner if Nova only continued with the delete if a
  PortNotFound is raised, but otherwise fails, which would result in the
  Instance remaining in a Error state with an entry in the
  instance_fault table so that the user can address the issue or at
  least re-try the delete.

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