yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1226336] Re: interruped vm delete operation leads to active but unaccessable vm

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: melanie witt <1226336@xxxxxxxxxxxxxxxxxx>
Date: Tue, 11 Nov 2014 23:24:52 -0000
Reply-to: Bug 1226336 <1226336@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

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

** This bug has been marked a duplicate of bug 1180178
   Instance IP addresses are re-used even when previous instance could not be powered off

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

Title:
  interruped vm delete operation leads to active but unaccessable vm

Status in OpenStack Compute (Nova):
  Incomplete

Bug description:
  version: essex (2012.1) and grizzly (2013.1)

  During a VM deletion, if nova-compute crashes (and then restarts)
  after sending a RPC cast/call (depending on essex/grizzly) to nova-
  network, demanding the latter to release the network resources
  assigned to the to-be-deleted VM, then the VM may remain active but
  lose network accessibility.

  Garbage collection logic may be improved to reap such inaccessible
  VMs. Otherwise users may be billed for keeping them running.

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