When creating a backup and it fails we will try
to update the status on the volume but if it does
not exist we will instead fail on that and the
backup will be stuck in creating status which means
cloud admin need to help resetting the status.
This catches the VolumeNotFound exception and ignores
updating the volume status and thus backup will be
set to error and can be deleted by user instead.
Reviewed: https:/ /review. opendev. org/c/openstack /cinder/ +/864100 /opendev. org/openstack/ cinder/ commit/ 813df9b99f23bdc 54787a0c918e47f 9d61df3232
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 813df9b99f23bdc 54787a0c918e47f 9d61df3232
Author: Tobias Urdin <email address hidden>
Date: Wed Nov 9 11:14:03 2022 +0100
Set backup status to error on VolumeNotFound
When creating a backup and it fails we will try
to update the status on the volume but if it does
not exist we will instead fail on that and the
backup will be stuck in creating status which means
cloud admin need to help resetting the status.
This catches the VolumeNotFound exception and ignores
updating the volume status and thus backup will be
set to error and can be deleted by user instead.
Closes-Bug: #1996049 3af257c1702df50 29469b11739
Change-Id: Iafa92ece7f8332