Quantum client needs to return a richer set of exceptions

Bug #1178734 reported by Phil Day on 2013-05-10
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

Currently pretty much any error in Quantum (like an API validation error) or even failing to talk to the API itself results in the same exception being raised, which means that Nova ends up reporting a 500 error for all problems.

The quantum client needs to raise the set of exception used by the Nova network API so that Nova can do a better job of reporting quantum errors

Phil Day (philip-day) wrote :

For example:

Use case: Adding a floating IP to a VM.

If the tenant network is not attached to the router, quantum client reports:
QuantumClientException: External network 7da74520-9d5e-427b-a508-213c84e69616 is not reachable from subnet 7760b25c-861e-4f60-8097-3d8ae65d9d6c. Therefore, cannot associate Port 61934195-e4e8-4bf2-a0d4-273b578f2794 with a Floating IP.

However nova only reports:
ERROR: Error. Unable to associate floating ip (HTTP 400) (Request-ID: req-75a4dbcb-9302-4868-b32a-69b48a45b559)
It would be useful to have the entire error in this case.

ZhiQiang Fan (aji-zqfan) wrote :

i think it is not a bug, and may be you should file it as a blueprint?

Akihiro Motoki (amotoki) wrote :

It is more than two years old.
Since then many improvements in both nova and neutronclient have been done.

Changed in python-neutronclient:
status: New → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for python-neutronclient because there has been no activity for 60 days.]

Changed in python-neutronclient:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers