Invalid keyname translated to null on create server
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Invalid
|
Low
|
Unassigned |
Bug Description
Invalid keyname translated to null on create server
400 bad request should raise for the case a user mistype keyname.
Test:
curl -i -H "x-auth-token: $AUTHTOKEN" -H "content-type: application/json" -d '{"server"
HTTP/1.1 202 Accepted
Content-Type: application/json
Content-Length: 718
Date: Wed, 16 Nov 2011 23:49:50 GMT
{"server": {"status": "BUILD", "updated": "2011-11-
Changed in nova: | |
importance: | Undecided → Low |
status: | New → Confirmed |
Changed in nova: | |
status: | Confirmed → In Progress |
assignee: | nobody → Brian Waldon (bcwaldon) |
milestone: | none → essex-4 |
Changed in nova: | |
assignee: | Brian Waldon (bcwaldon) → nobody |
status: | In Progress → Incomplete |
milestone: | essex-4 → none |
I'd think the right behavior here is to fail with a 4xx exception on boot. Do you agree?