Shuicheng Lin 1faff551f2 catch the correct exception for alarm not found case ... Issue: for the alarm_show/alarm_delete/event_show api, if the input UUID string is not valid, http server side will return error code 500 (Internal Server Error), due to the error code is not set correctly. Solution: Correct the error code in server, and add client code to handle "HTTP 404 - Not Found" error code correctly. Test: Run "fm alarm-show/alarm-delete/event-show" with valid/invalid UUID, and the response is correct. For invalid UUID, response string will like below. "xxx" for the invalid UUID string. "Alarm not found: xxx" "Event log not found: xxx" Closes-Bug: 1806927 Change-Id: I8d17c5bc55733f269d875ae835ab6295fed4d899 Signed-off-by: Shuicheng Lin <shuicheng.lin@intel.com>		2019-03-18 20:10:37 +08:00
..
centos	catch the correct exception for alarm not found case	2019-03-18 20:10:37 +08:00
fmclient	catch the correct exception for alarm not found case	2019-03-18 20:10:37 +08:00
PKG-INFO	Update the License in FM packages	2018-09-05 14:54:00 -04:00