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'.
Reviewed: https:/ /review. openstack. org/369982 /git.openstack. org/cgit/ openstack/ magnum/ commit/ ?id=9f7295475dc d7a30eef18fa2dd b05bed036fef23
Committed: https:/
Submitter: Jenkins
Branch: master
commit 9f7295475dcd7a3 0eef18fa2ddb05b ed036fef23
Author: Madhuri Kumari <email address hidden>
Date: Wed Sep 14 20:19:43 2016 +0530
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: Iad6e8bfce7326b 34dea04914e4552 f87d2796e86
Closes-bug: #1623387