Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
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 Change-Id: Iafa92ece7f83323af257c1702df5029469b11739 (cherry picked from commit 813df9b)
- Loading branch information
1 parent
0d562ba
commit 5f35750
Showing
3 changed files
with
34 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
5 changes: 5 additions & 0 deletions
5
releasenotes/notes/backup-volumenotfound-set-to-error-fa47b3631093a702.yaml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
--- | ||
fixes: | ||
- | | ||
`Bug #1996049 <https://bugs.launchpad.net/cinder/+bug/1996049>`_: Fixed bug | ||
where backup was not set to error on failure when volume did not exist. |