yahoo-eng-team team mailing list archive

["Markus Zoeller \(markus_z\)" <mzoeller@xxxxxxxxxxxxxxxxxx>]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY


** Changed in: nova
   Importance: Low => Undecided

** Changed in: nova
       Status: Confirmed => Expired

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

Title:
  nova should delete neutron ports before calling unplug_vifs

Status in OpenStack Compute (nova):
  Expired

Bug description:
  Currently nova unplugs the vifs of neutron ports first and then
  deletes the ports in neutron. Because of this it's possible for
  neutron to detect that the port has gone down and then notify nova of
  this change. During this time the instance will probably already be
  deleted. We should probably change the order of events in nova-compute
  do do port-delete in neutron then vif-uplugged()

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