OSAPI v1.1 PUT /servers/<id> response incorrect
Bug #824601 reported by
Brian Waldon
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Johannes Erdfelt |
Bug Description
Using version 1.1 of the compute API
I have an active server with id of: 3
When updating the name of a Server using a PUT request (/v1.1/servers/3) the server name gets updated just fine, but the response is a "204 No Content"
The OpenStack Compute Dev Guide V1.1 (4.1.4. Update Server) lists the following response codes:
Normal Response Code(s): 200
Error Response Code(s): computeFault (400, 500, …), serviceUnavailable (503),
unauthorized (401), forbidden (403), badRequest (400), badMethod (405), overLimit (413),
itemNotFound (404), badMediaType (415), buildInProgress (409)
The spec also requires the updated server entity in the response. Currently, no body is returned.
Related branches
lp:~johannes.erdfelt/nova/lp824601
- Brian Waldon (community): Approve
- Devin Carlen (community): Approve
-
Diff: 136 lines (+29/-19)2 files modifiednova/api/openstack/servers.py (+11/-8)
nova/tests/api/openstack/test_servers.py (+18/-11)
summary: |
- OSAPI v1.1 PUT /servers/<id> response code incorrect + OSAPI v1.1 PUT /servers/<id> response incorrect |
description: | updated |
Changed in nova: | |
assignee: | nobody → Johannes Erdfelt (johannes.erdfelt) |
Changed in nova: | |
status: | New → Fix Committed |
Changed in nova: | |
milestone: | none → diablo-4 |
Changed in nova: | |
milestone: | diablo-4 → 2011.3 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.