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) |
To post a comment you must log in.
Fix proposed to branch: master /review. opendev. org/695357
Review: https:/