OS API: 404 when using a non-existing flavor in the filter for list servers

[Daryl Walleck]

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-3995-4cfb-a579-7cd8f336a663" http://localhost:8774/v1.1/15/servers?flavor=999
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}}

[Brian Waldon (bcwaldon)]

Yep, this makes sense.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/3256

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/3256
Committed: http://github.com/openstack/nova/commit/d7448fc86a929226a34e92ef77684441f451edaf
Submitter: Jenkins
Branch: master

commit d7448fc86a929226a34e92ef77684441f451edaf
Author: Brian Waldon <email address hidden>
Date: Fri Jan 20 17:02:19 2012 -0800

    Handle FlavorNotFound on server list w/ filter

    Fix bug 919426

    Change-Id: I1f450fd7ed28837b664aa81f4dd833e3433cd126