yahoo-eng-team team mailing list archive

[zhaoleilc <1971405@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Description
===========
There will be redundant bdms in nova after a volume
fails to be detached from the server, ie, the libvirt
has succeeded in detaching the disk and attachment
in cinder has disappeared, but bdm in nova is present.
In such scenario, nova compute service will report an
error that device vdb not found in instance if the 
volume is detached from the server again.

Expected result
===============
Even though redundant bdms are present, they can be 
removed by another volume remove operation. Or these
bdms reside in nova database forever until the database
is directly modified.

** Affects: nova
     Importance: Undecided
         Status: New

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

Title:
  Get stuck in detaching state due redundant bdm

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===========
  There will be redundant bdms in nova after a volume
  fails to be detached from the server, ie, the libvirt
  has succeeded in detaching the disk and attachment
  in cinder has disappeared, but bdm in nova is present.
  In such scenario, nova compute service will report an
  error that device vdb not found in instance if the 
  volume is detached from the server again.

  Expected result
  ===============
  Even though redundant bdms are present, they can be 
  removed by another volume remove operation. Or these
  bdms reside in nova database forever until the database
  is directly modified.

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