Fix wrong usage of fields.BackupStatus.AVAILABLE
This patch is to fix the wrong usage of fields.BackupStatus.AVAILABLE in cinder\backup\manager.py, changed to use fields.SnapshotStatus.AVAILABLE. Change-Id: I4a8d795a4c46c3159cdd8508e0c5e5c921365ceb
This commit is contained in:
parent
03a6edffd8
commit
9b3f2f136f
|
@ -423,8 +423,9 @@ class BackupManager(manager.ThreadPoolManager):
|
|||
|
||||
# Restore the original status.
|
||||
if snapshot_id:
|
||||
self.db.snapshot_update(context, snapshot_id,
|
||||
{'status': fields.BackupStatus.AVAILABLE})
|
||||
self.db.snapshot_update(
|
||||
context, snapshot_id,
|
||||
{'status': fields.SnapshotStatus.AVAILABLE})
|
||||
else:
|
||||
self.db.volume_update(context, volume_id,
|
||||
{'status': previous_status,
|
||||
|
|
Loading…
Reference in New Issue