Consider volume in 'reserved' status as detachment in progress
It's possible that a volume can end up in `reserved` state when volume attachment fails. We should wait for it to be available when detaching. Change-Id: Ieb1d12ea9d7c8c76c448387fadfb2e4dbf4cbb2e Story: #2003789 Task: 26497
This commit is contained in:
parent
dd9fbb0487
commit
ff83aaeeb4
|
@ -140,7 +140,7 @@ class CinderClientPlugin(client_plugin.ClientPlugin):
|
|||
if server_id and server_id not in server_ids:
|
||||
return True
|
||||
|
||||
if vol.status in ('in-use', 'detaching'):
|
||||
if vol.status in ('in-use', 'detaching', 'reserved'):
|
||||
LOG.debug('%s - volume still in use', vol_id)
|
||||
return False
|
||||
|
||||
|
|
Loading…
Reference in New Issue