yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1492121] Re: VMware: failed volume detachment leads to instances remaining on backend and volume still in 'in-use' state

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>
Date: Thu, 24 Sep 2015 07:00:17 -0000
Reply-to: Bug 1492121 <1492121@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

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

** Changed in: nova
    Milestone: None => liberty-rc1

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

Title:
  VMware: failed volume detachment leads to instances remaining on
  backend and volume still in 'in-use' state

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Security Advisory:
  Won't Fix

Bug description:
  When the volume detachment fails the termination of the instance will lead to the following:
  1. The Nova instance is deleted
  2. The Instance on the VC still exists
  3. The volume is in 'in-use' state

  The nova instance is deleted but the backend is not updated and the
  volumes are not set as available

  One example of this happening is when the spawning of the instance fails with an exception when attaching the volume.
  This issue could lead to a DDOS of the backend as the resources on the backend are not cleaned up correctly.

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