Cinder doesn't correctly handle None values in set quota
Bug #1451637 reported by
Jamie Lennox
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Triaged
|
Undecided
|
Unassigned |
Bug Description
Prior to openstackclient 1.1.0 when you did a quota set it would send None values to cinder for options it didn't want to change. Cinder would reject this change with a generic 400 bad client response.
There are two parts to this:
1. Cinder should return an appropriate error like it does when you try to set a non-integer value to a quota.
2. Should cinder ignore None values in a quota set?
Changed in cinder: | |
assignee: | nobody → Karthik Prabhu Vinod (karthik-prabhu-vinod) |
Changed in cinder: | |
assignee: | Karthik Prabhu Vinod (karthik-prabhu-vinod) → nobody |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/180003
Review: https:/