Nova quota-update fails with HTTP 400
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-novaclient |
Fix Released
|
Critical
|
Sean Dague |
Bug Description
If I do:
nova --debug quota-update --cores 400 ffd146506e2444d
I get:
ERROR: Bad key(s) force in quota_set (HTTP 400) (Request-ID: req-5ecdd1c8-
Request and response body are:
REQUEST BODY: {"quota_set": {"force": false, "tenant_id": "ffd146506e2444
RESP: [400] {'date': 'Fri, 26 Apr 2013 19:12:53 GMT', 'content-length': '73', 'content-type': 'application/json; charset=UTF-8', 'x-compute-
RESP BODY: {"badRequest": {"message": "Bad key(s) force in quota_set", "code": 400}}
Stacktrace is:
DEBUG (shell:768) Bad key(s) force in quota_set (HTTP 400) (Request-ID: req-5ecdd1c8-
Traceback (most recent call last):
File "/opt/stack/
OpenStackCo
File "/opt/stack/
args.
File "/opt/stack/
_quota_
File "/opt/stack/
manager.
File "/opt/stack/
return self._update(
File "/opt/stack/
_resp, body = self.api.
File "/opt/stack/
return self._cs_
File "/opt/stack/
**kwargs)
File "/opt/stack/
resp, body = self.request(url, method, **kwargs)
File "/opt/stack/
raise exceptions.
BadRequest: Bad key(s) force in quota_set (HTTP 400) (Request-ID: req-5ecdd1c8-
This happens on trunk.
If I edit the server code to allow 'force' as _good_ key, the operation goes through just fine, but I am not 100% sure if that's the right fix.
Changed in nova: | |
assignee: | nobody → Armando Migliaccio (armando-migliaccio) |
Changed in python-novaclient: | |
status: | Fix Committed → Fix Released |
It looks like there was a fix that jumped the gun:
(client-side) https:/ /review. openstack. org/#/c/ 26365/
whereas:
(server-side) https:/ /review. openstack. org/#/c/ 25887/
hasn't quite made it.
I am duplicating this bug