yahoo-eng-team team mailing list archive

Thread
Date

[Bug 2089034] [NEW] The share is not marked as an error if the VM fails to delete

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Uggla <2089034@xxxxxxxxxxxxxxxxxx>
Date: Tue, 19 Nov 2024 15:24:59 -0000
Reply-to: Bug 2089034 <2089034@xxxxxxxxxxxxxxxxxx>
Sender: noreply@xxxxxxxxxxxxx

Public bug reported:

Description
===========
If the instance is put into an ERROR state during instance deletion because the Manila shares could not be cleaned up, set the related share_mapping to ERROR as well to signal the reason for the failed instance deletion.


https://review.opendev.org/c/openstack/nova/+/833090/comments/3bb2d18e_fd89e1e1

Expected result
===============
Instance and Share set to error

Actual result
=============
Only instance is set to error

Environment
===========
Epoxy
DevStack

** Affects: nova
     Importance: Undecided
         Status: Triaged

** Changed in: nova
       Status: New => Triaged

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

Title:
  The share is not marked as an error if the VM fails to delete

Status in OpenStack Compute (nova):
  Triaged

Bug description:
  Description
  ===========
  If the instance is put into an ERROR state during instance deletion because the Manila shares could not be cleaned up, set the related share_mapping to ERROR as well to signal the reason for the failed instance deletion.

  
  https://review.opendev.org/c/openstack/nova/+/833090/comments/3bb2d18e_fd89e1e1

  Expected result
  ===============
  Instance and Share set to error

  Actual result
  =============
  Only instance is set to error

  Environment
  ===========
  Epoxy
  DevStack

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