Error messages are not displayed correctly for segment create and host create
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-masakariclient |
Fix Released
|
High
|
Dinesh Bhor |
Bug Description
Error messages should be user friendly and self explanatory.
For the following commands proper error messages are returned from masakari-api service but the error message is not displayed correctly at masakariclient side:
1) If the host is already present with the same name:
dopenstack@
OUTPUT:
HttpException: Conflict
2) If the segment is already present with the same name:
dopenstack@
OUTPUT:
HttpException: Conflict
3) If the recovery_method of the segment is invalid:
dopenstack@
OUTPUT:
HttpException: Bad Request
4) If the service_type value of segment is too large(greater than 255 characters)
dopenstack@
OUTPUT:
HttpException: Bad Request
5) If the segment itself is not present while creating host:
dopenstack@
OUTPUT:
NotFoundException: Not Found
Expected Output: In all the above cases, the error message returned from the masakari-api service should be displayed at the masakari client side.
Changed in python-masakariclient: | |
assignee: | nobody → Dinesh Bhor (dinesh-bhor) |
Changed in python-masakariclient: | |
status: | New → Confirmed |
importance: | Undecided → High |
description: | updated |
This issue was there in python-openstacksdk and fixed in the following patch: https:/ /review. openstack. org/#/c/ 420722/
The fix is available in python-openstacksdk 0.9.13