yahoo-eng-team team mailing list archive

[OpenStack Infra <2019078@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/c/openstack/nova/+/882284
Committed: https://opendev.org/openstack/nova/commit/9d5935d007e5a50a4fd61ad033cd0135fdcaa2eb
Submitter: "Zuul (22348)"
Branch:    master

commit 9d5935d007e5a50a4fd61ad033cd0135fdcaa2eb
Author: Amit Uniyal <auniyal@xxxxxxxxxx>
Date:   Thu May 4 12:41:00 2023 +0000

    Delete dangling bdms
    
    On reboot, check the instance volume status on the cinder side.
    Verify if volume exists and cinder has an attachment ID, else
    delete its BDMS data from nova DB and vice versa.
    
    Updated existing test cases to use CinderFixture while rebooting as
    reboot calls get_all_attachments
    
    Implements: blueprint https://blueprints.launchpad.net/nova/+spec/cleanup-dangling-volume-attachments
    Closes-Bug: 2019078
    
    Change-Id: Ieb619d4bfe0a6472aefb118b58283d7ad8d24c29


** Changed in: nova
       Status: In Progress => Fix Released

-- 
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):
  Fix Released

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