Madhuri Kumari 9f7295475d Add exceptions to cluster db to show failures ... After changing create to async operation, all the exceptions goes hidden and no db entry is created to show the actual failure. One has to go through the logs to find the actual error. This patch creates a db entry in cluster table to show the actual error in column 'status_reason'. Change-Id: Iad6e8bfce7326b34dea04914e4552f87d2796e86 Closes-bug: #1623387		2016-09-14 20:27:10 +05:30
..
handlers	Add exceptions to cluster db to show failures	2016-09-14 20:27:10 +05:30
tasks	Fix invalid import order	2016-02-07 22:54:41 -08:00
__init__.py	Make room for functional tests	2015-04-02 12:25:43 -04:00
test_k8s_api.py	Code refactoring in conductor/k8s_api.py	2016-05-18 01:55:20 +05:30
test_monitors.py	Rename Bay DB, Object, and internal usage to Cluster	2016-09-08 13:01:12 -07:00
test_rpcapi.py	Rename Bay DB, Object, and internal usage to Cluster	2016-09-08 13:01:12 -07:00
test_scale_manager.py	Rename Bay DB, Object, and internal usage to Cluster	2016-09-08 13:01:12 -07:00
test_utils.py	Rename Bay DB, Object, and internal usage to Cluster	2016-09-08 13:01:12 -07:00