Tempest Shares client should catch error_delete status for other resources
Bug #1477703 reported by
Andrew Kerr
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
Low
|
Andrew Kerr |
Bug Description
The shares client in tempest currently catches if a share is in 'error_deleting'
state and throws a ResourceRelease
to wait for the timeout.
However, more resources than just shares can go into error_deleting state,
snapshots for example
description: | updated |
Changed in manila: | |
milestone: | none → liberty-2 |
importance: | Undecided → Low |
Changed in manila: | |
status: | Fix Committed → Fix Released |
Changed in manila: | |
milestone: | liberty-2 → 1.0.0 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/206116
Review: https:/