<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 07/11/14 04:17, Tao Tao wrote:<br>
</div>
<blockquote
cite="mid:OFBC02FD25.778B752D-ON85257D89.001118B4-85257D89.00121B44@us.ibm.com"
type="cite">
<p>Hi, Henry:<br>
<br>
Appreciate very much for your kind reply!<br>
<br>
Yes, this is what I want, however, I am not seeing the detailed
error message as you are seeing.<br>
<br>
I am still using OpenStack Icehouse, are you using OpenStack
Juno or Icehouse?<br>
<br>
[root@openstack-03 heat(keystone_admin)]# heat stack-show
LCH_test1<br>
+----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------+<br>
| Property | Value
|<br>
+----------------------+--------------------------------------------------------------------------------------------------------------------------------
|<br>
| stack_status_reason | Resource CREATE failed: Error:
Deployment to server
|<br>
| | failed: deploy_status_code : Deployment
exited with
|<br>
| | non-zero status code: 1
|<br>
|<br>
+----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------+<br>
<br>
</p>
> <br>
> What I really mean is how to expose the error messages so
that I can<br>
> use Heat REST API to find the error messages?<br>
> <br>
> In another word, how would a user to be able to find out the
<br>
> specific error message as a Heat client?<br>
> <br>
><br>
</blockquote>
<br>
The deployment resource has attributes deploy_status_code,
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
deploy_stderr and <br>
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
deploy_stdout [1]. Currently you will need to create stack outputs
in your template to expose these properties then use heat stack-show
to see their values.<br>
<br>
There are blueprints for Kilo which will make it possible to access
these values in different ways without having to modify your heat
template [2].<br>
<br>
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
[1]
<a class="moz-txt-link-freetext" href="http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Heat::SoftwareDeployment">http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Heat::SoftwareDeployment</a><br>
[2] <a class="moz-txt-link-freetext" href="https://review.openstack.org/#/c/130679/">https://review.openstack.org/#/c/130679/</a><br>
<a class="moz-txt-link-freetext" href="https://review.openstack.org/#/c/121979/">https://review.openstack.org/#/c/121979/</a><br>
</body>
</html>