yahoo-eng-team team mailing list archive

[Amit Uniyal <2019078@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

A live migration failure created a scenario when the volume is deleted
from the system but its BDM is present in Nova DB.


Nova does not support deleting a volume that is attached to a VM.

On rebooting Nova failed to find the volume listed as attached in DB and
the instance ended up going to an error state.

In order to remove the volume that has already been deleted, operator
has to shutdown Vm and then delete the bdm from DB manually.


Environment
===========
Train release


Logs & Configs
==============
https://paste.opendev.org/show/bnGkFSsConbbLpynbdfp/


@gibi filed a blueprint for same https://blueprints.launchpad.net/nova/+spec/nova-manage-cleanup-dangling-volume-attachments

** 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/2019078

Title:
  cleanup up dangling volume attachment

Status in OpenStack Compute (nova):
  New

Bug description:
  A live migration failure created a scenario when the volume is deleted
  from the system but its BDM is present in Nova DB.

  
  Nova does not support deleting a volume that is attached to a VM.

  On rebooting Nova failed to find the volume listed as attached in DB
  and the instance ended up going to an error state.

  In order to remove the volume that has already been deleted, operator
  has to shutdown Vm and then delete the bdm from DB manually.

  
  Environment
  ===========
  Train release

  
  Logs & Configs
  ==============
  https://paste.opendev.org/show/bnGkFSsConbbLpynbdfp/

  
  @gibi filed a blueprint for same https://blueprints.launchpad.net/nova/+spec/nova-manage-cleanup-dangling-volume-attachments

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