Replace the value of None with 'error_extending' when scheduler failed to extend volume.
Bug #1853394 reported by
haixin
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Cinder |
In Progress
|
Undecided
|
haixin | ||
Bug Description
In the process of volume extend, if schedule could not find any available weighted backend,it rollback volume status to available or in-use, but the previous status set to None, it is unreasonable, because user had try to extend volume, but not success, so previous status should be error_extending.
| Changed in cinder: | |
| assignee: | nobody → haixin (haixin77) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to cinder (master) | #1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on cinder (master) | #2 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to cinder (master) | #3 |
| Changed in cinder: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on cinder (master) | #4 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/