No error's reported if heat stack creation/update fails

[Steve McLellan]

If heat stack creation fails, there's no indication available why, other than looking at the heat resource list. It looks like it would be reasonably simple to examine the stack_status_reason from heat stack-show and use that, or in the instance of an exception from heatclient, use the heat client exception. This could then appear in the deployment history and/or the last status update field.

[Stan Lagun (slagun)]

Actually Heat errors are reported. Heat python-client throw exceptions with meaningful messages that are caught at environment level and reported to API/dashboard. To see them you need to go to Environments -> %your_env% - > Deployment History tab -> Show details -> Logs tab. On attached screenshot you can see how it looks in my browser. There is definitely a problem with dashboard usability though

[Stan Lagun (slagun)]

After a further research I saw that this works only with errors that caught by Heat stack validation code and the reason for deployment-time errors are not shown

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/124426

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/124426
Committed: https://git.openstack.org/cgit/stackforge/murano/commit/?id=f901e9acfa4d571283134a863ca68ff34819138d
Submitter: Jenkins
Branch: master

commit f901e9acfa4d571283134a863ca68ff34819138d
Author: Stan Lagun <email address hidden>
Date: Fri Sep 26 18:47:47 2014 +0400

    No error's reported if heat stack creation/update fails

    Adds error status reason text to exception message that is raised
    when Heat stack create/update fails

    Also disables stack rollback for consistency (otherwise if error happens during
    stack creation it silently disappears and no reason provided)

    Change-Id: Ia4366cba486e9ce4c5ae35ecb3e042bbf5f7ef3d
    Closes-Bug: #1369722