Quota set sends invalid messages
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-openstackclient |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Calling:
# openstack --debug --os-identity-
on OSC 1.0.3 results in a request that looks like:
'{"quota_set": {"gigabytes": null, "tenant_id": "9d33152f0d2740
There are two problems here:
1. Cinder cannot handle Null values for its values and returns a 400 which fails the command
2. OSC should not send this request to cinder if there are no cinder values present.
The problem is that we build the quota set requests using getattr(key, val, None) and do not check the return and so we create a full dictionary with None values for options we do not wish to change.
This was fixed for volume in OSC 1.1.0 as a side effect of bug 1438377 where you can see the addition of the if value check, however this does not get backported into the stable 1.0 series.
The problem still affects compute in master.
description: | updated |
tags: | added: kilo-backport-potential |
description: | updated |
Changed in python-openstackclient: | |
milestone: | none → m11 |
Changed in python-openstackclient: | |
status: | Fix Committed → Fix Released |
Changing the title as this same problem will apply to compute in current master, I do not know if compute raises a similar error though.