Several errors in network operations should be taken as NetworkException instead of InvalidInput
Bug #1770084 reported by
dyyang@cn.ibm.com
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| zVM Cloud Connector |
Fix Committed
|
Low
|
Ya Lian Pan | ||
Bug Description
We only define three types of invalid input error: invalid format/type/number.
Currently in network interfaces, a new exception named InvalidInput is added and used a lot. There are several error cases (eg, specified OSA is not free, active is specified True when guest is in 'off' status, etc.) are wrongly reported as invalidinput error, which should be NetworkOperatio
Revision history for this message
| dyyang@cn.ibm.com (dyyang) wrote | #1 |
| Changed in python-zvm-sdk: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| assignee: | nobody → Ya Lian Pan (yalian) |
| Changed in python-zvm-sdk: | |
| status: | Triaged → In Progress |
Revision history for this message
| jichenjc (jichenjc) wrote | #2 |
| Changed in python-zvm-sdk: | |
| status: | In Progress → Fix Committed |
To post a comment you must log in.
After more discussion, all module exceptions (NetworkOperati
We should avoid 500 as possible, so all these kind of resource status error should be reported as Conflict exception.