Quantum client needs to return a richer set of exceptions
Bug #1178734 reported by
Phil Day
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-neutronclient |
Expired
|
Undecided
|
Unassigned |
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
To post a comment you must log in.
For example:
Use case: Adding a floating IP to a VM.
If the tenant network is not attached to the router, quantum client reports: ception: External network 7da74520- 9d5e-427b- a508-213c84e696 16 is not reachable from subnet 7760b25c- 861e-4f60- 8097-3d8ae65d9d 6c. Therefore, cannot associate Port 61934195- e4e8-4bf2- a0d4-273b578f27 94 with a Floating IP.
QuantumClientEx
However nova only reports: 9302-4868- b32a-69b48a45b5 59)
ERROR: Error. Unable to associate floating ip (HTTP 400) (Request-ID: req-75a4dbcb-
It would be useful to have the entire error in this case.