Exceptions in quantumclient are inconsistently defined
Bug #987586 reported by
Maru Newby
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard (Horizon) |
Invalid
|
Low
|
Unassigned | ||
neutron |
Invalid
|
Low
|
yong sheng gong | ||
python-neutronclient |
Invalid
|
Medium
|
Unassigned |
Bug Description
As per the suggestions in the following review:
https:/
- Merge QuantumClientEx
- Ensure that all exceptions define a default message
- Remove the 'Client' qualifier from the name of all exceptions
Changed in quantum: | |
status: | Confirmed → Invalid |
Changed in python-quantumclient: | |
assignee: | nobody → Roman Podolyaka (rpodolyaka) |
Changed in python-quantumclient: | |
importance: | Undecided → Medium |
Changed in horizon: | |
status: | New → Confirmed |
importance: | Undecided → Low |
milestone: | none → havana-1 |
Changed in horizon: | |
milestone: | havana-1 → havana-2 |
Changed in horizon: | |
milestone: | havana-2 → havana-3 |
Changed in horizon: | |
milestone: | havana-3 → none |
Changed in python-neutronclient: | |
assignee: | Roman Podoliaka (rpodolyaka) → nobody |
status: | In Progress → Confirmed |
Changed in horizon: | |
assignee: | Roman Podoliaka (rpodolyaka) → nobody |
To post a comment you must log in.
Yong, can you comment on whether this still matters with the new version of the client? If so, we can keep it, otherwise, please mark as invalid.