Associating non-existant floating ip used to return 500 error code. Now returns 400 instead of 404
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Invalid
|
Low
|
shilpa batchu |
Bug Description
Steps to reproduce:
> (run devstack)
> launch instance
> nova add-floating-ip [server_id] 172.24.4.22 # this address is not in db
Expected:
Error message stating that the address does not exist or some such
Actual:
ERROR: Associate floating ip failed (HTTP 500)
In nova-network:
2012-03-16 22:44:29 INFO nova.api.
2012-03-16 22:44:29 INFO nova.api.
A not found exception would be helpful to let the user know that she entered the address incorrectly.
tags: | added: essex-rc-potential |
Changed in nova: | |
status: | New → Triaged |
importance: | Undecided → Low |
Changed in nova: | |
assignee: | nobody → shilpa batchu (shilpa-batchu) |
status: | Triaged → In Progress |
tags: | removed: essex-rc-potential |
summary: |
- Associating non-existant floating ip yields 500 + Associating non-existant floating ip used to return 500 error code. Now + returns 400 instead of 404 |
Fix proposed to branch: master /review. openstack. org/6367
Review: https:/