Inconsistent error messages for segment host show
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-masakariclient |
Confirmed
|
Medium
|
Hussain Chachuliya |
Bug Description
There is inconsistency in error messages that is displayed to the user via masakari-client and the one displayed in masakari-api service logs.
If user passes non-existing segment id to the "host show" command, then user should get proper error message saying "No failover segment with id <id>" instead of "Host not found: <hostname>" as it might confuse user if host name passed to the command is really existing.
Steps to reproduce:
-------------------
1. Execute segment host show command with a non-existing segment ID.
* From masakari-client:
$ openstack segment host show abc abb
Host not found: abb
* From masakari-api service logs:
2017-01-03 12:19:22.780 INFO masakari.
Expected output:
----------------
$ openstack segment host show abc abb
No failover segment with id abc.
description: | updated |
Changed in python-masakariclient: | |
assignee: | nobody → Hussain Chachuliya (hussainchachuliya) |
description: | updated |
description: | updated |
If user passes non-existing segment id to the "host show" command, then user should get proper error message saying "no failover segment with id <id>" instead of "host not found: <hostname>" as it might confuse user if host name passed to the command is really existing.