Failed retype with driver raised exception should set volume status to "error"
Bug #1305550 reported by
Li Min Liu
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Opinion
|
Undecided
|
Unassigned |
Bug Description
When retype volume, if driver does not support this feature, will return False, cinder-volume will create a new copy of the volume and copy data to the the new one.
If driver raise exception, it should report error and set volume status as "error", should not fall back to generic mechanism
Changed in cinder: | |
assignee: | nobody → Li Min Liu (liminliu) |
description: | updated |
summary: |
- retype failed when driver rise exception + Failed retype with driver raise exception should set volume status to + "error" |
summary: |
- Failed retype with driver raise exception should set volume status to + Failed retype with driver raised exception should set volume status to "error" |
Changed in cinder: | |
status: | New → In Progress |
Changed in cinder: | |
status: | In Progress → Opinion |
To post a comment you must log in.
https:/ /review. openstack. org/#/c/ 84991/