Neutron driver handles incorrectly 404 errors
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Cedric Brandily |
Bug Description
Neutronclient transforms errors using exception_
In particular, it transforms 404 responses into:
1) [2] neutronclient.
2) [3] neutronclient.
Nova neutron driver[4] supports mostly 1) but not 2).
But Neutron in case of 404 returns the following body:
{"message": "The resource could not be found.<br /><br />\n\n\n", "code": "404 Not Found", "title": "Not Found"}
and we end in 2) and Nova Neutron driver doesn't catch the error correctly and raises a 500
You can reproduce it indirectly using:
openstack server add fixed ip <vm> <network-name>
which queries:
nova-base-
assuming it would return the network or a 404 but it returns 500.
This trouble can be solved by catching NotFound instead of NetworkNotFound
[1] https:/
[2] https:/
[3] https:/
[4] nova.network.
Changed in nova: | |
assignee: | nobody → Cedric Brandily (cbrandily) |
description: | updated |
Changed in nova: | |
status: | New → Confirmed |
importance: | Undecided → Low |
tags: | added: low-hanging-fruit neutron |
Also got this issue in production.
openstack server add fixed ip <vm> <network-name> always results in 500.
We use Newton release, and need a bugfix ASAP.