You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
novaclient.exceptions.BadRequest: Invalid volume: Invalid input received: Invalid volume: Unable to detach volume. Volume status must be 'in-use' and attach_status must be 'attached' to detach.
#1048
Open
freyes opened this issue
May 15, 2023
· 0 comments
When the test is tearing down the resources, it's assuming that the dettach operation is fast, it's not blocking until that state reaches available, so the next call to delete the volume fails
Before this change during the tearDown process there is an assumption
that a volume can be deleted right after has ben detached, although
there is a transitional state called "detaching" which is more
noticeable on slow environments.
This change makes sure to wait for the volume to reach to the
'available' status before attempting the deletion.
Closesopenstack-charmers#1048
When the test is tearing down the resources, it's assuming that the dettach operation is fast, it's not blocking until that state reaches
available
, so the next call to delete the volume failsThe function
detach_volume()
should block after callingnova.volumes.delete_server_volume()
until the volume gets to available state - https://github.com/openstack-charmers/zaza-openstack-tests/blob/master/zaza/openstack/utilities/openstack.py#L2753The text was updated successfully, but these errors were encountered: