OS API: 404 when using a non-existing flavor in the filter for list servers
Bug #919426 reported by
Daryl Walleck
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Brian Waldon |
Bug Description
When I pass a flavor that isn't in my Nova system as a filter for a list server request, a 404 is returned. I'm assuming this is because it tries to do a lookup on the flavor first. I would expect this to just return the empty list.
Example:
curl -i -H "X-Auth-Token: 2dc9ffd0-
HTTP/1.1 404 Not Found
Content-Length: 78
Content-Type: application/json; charset=UTF-8
Date: Fri, 20 Jan 2012 22:30:22 GMT
Connection: close
{"itemNotFound": {"message": "The resource could not be found.", "code": 404}}
Changed in nova: | |
milestone: | none → essex-3 |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | essex-3 → 2012.1 |
To post a comment you must log in.
Yep, this makes sense.