The neutron client raises NeutronClientException (status_code 404)
that is not unknown for nova, and is translated in 500 computeFault.
Catching this exception in nova/nova/network/neutronv2/api.py and
raising more generic exception as exception.NotFound solves the problem.
Reviewed: https:/ /review. openstack. org/44445 github. com/openstack/ nova/commit/ ae8842c66e6bac0 3717bed62c644b7 c85708bf5a
Committed: http://
Submitter: Jenkins
Branch: stable/grizzly
commit ae8842c66e6bac0 3717bed62c644b7 c85708bf5a
Author: Ala Rezmerita <email address hidden>
Date: Thu Jul 18 11:48:36 2013 +0200
Fix inconsistency between Nova-Net and Neutron
The neutron client raises NeutronClientEx ception (status_code 404) network/ neutronv2/ api.py and
that is not unknown for nova, and is translated in 500 computeFault.
Catching this exception in nova/nova/
raising more generic exception as exception.NotFound solves the problem.
Added also an unitary test to test neutronv2 api
bug #1160309
bug #1200175
(cherry picked from commit 4a2915b4e389bfb a0ff25583369fd7 5b24e19118)
Conflicts: network/ quantumv2/ api.py
nova/
Change-Id: Ib2f1a0d49a1211 4b28f0cd5ce0bb7 119f864d1a6