cinder volume create with bad availability_zone should fail immediately
Bug #1185714 reported by
stephen mulcahy
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Low
|
Haomai Wang |
Bug Description
the cinder api accepts requests for volume creation specifying a non-existent availability_zone with the volume created going into the error state once the backend recognises that the availability zone doesn't exist. This error should be caught at the api and an error immediately returned to the user.
To reproduce in devstack:
cinder create --availability_zone badaz 1
(request accepted, volume creation begins)
cinder show <volume uuid>
volume in error state
Changed in cinder: | |
status: | New → Confirmed |
Changed in cinder: | |
importance: | Undecided → Low |
Changed in cinder: | |
assignee: | nobody → Vincent Hou (houshengbo) |
Changed in cinder: | |
milestone: | none → havana-2 |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | havana-2 → 2013.2 |
To post a comment you must log in.
Seems the request will failed by scheduler actually, will not go to backend.
I think this make sense ,no reason for API to keep a complete Availability-zone list