Dissociating a non-existant floating ip from a server throws a 500 instead of a 404

Bug #1060394 reported by Wayne Vestal Weeks
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Won't Fix
Medium
Unassigned

Bug Description

Description

remove floating ip 0.0.0.0 from a server results in Compute Fault 500 Instead of 404:

curl -D - -X POST -H 'x-auth-token: <TOKEN>' -H 'x-auth-project-id: CloudTester1' -H 'user-agent: Tester' -H 'accept: application/json' -H 'content-type: application/json' <Endpoint>/v2/YWhkdHXqeGwU6UNE8juB-PLe/servers/06c7d848-a052-49a0-8476-faa4746a121a/action -d '{"removeFloatingIp": {"address": "0.0.0.0"}}'
HTTP/1.1 500 Internal Server Error
Content-Length: 128
Content-Type: application/json; charset=UTF-8
X-Compute-Request-Id: req-8825d292-cd9e-492d-9745-287781d12ca9
Date: Tue, 02 Oct 2012 17:50:24 GMT

{"computeFault": {"message": "The server has either erred or is incapable of performing the requested operation.", "code": 500}

Revision history for this message
Russell Bryant (russellb) wrote :

Can you clarify what version of nova you were using? Thanks.

Changed in nova:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

That was Essex/stable.

Revision history for this message
Brian Waldon (bcwaldon) wrote :

I see a 404 on Folsom/Grizzly.

Revision history for this message
Michael Still (mikal) wrote :

Essex only gets security fixes now, and this doesn't seem to be security related.

Changed in nova:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.