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 813df9b99f)
6 lines
173 B
YAML
6 lines
173 B
YAML
---
|
|
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.
|