Open Stack

Hi, Tao Tao,

Here is an example,

DEBUG (session) REQ: curl -i -X GET
http://9.186.100.22:8004/v1/f334fc078b944b60a08d121022fae0f0/stacks/s1
... ...

RESP BODY:
{ "stack" : { "capabilities" : [  ],

      ... ...

      "parent" : null,
      "stack_name" : "s1",
      "stack_owner" : "admin",
      "stack_status" : "CREATE_FAILED",
      "stack_status_reason" : "Resource CREATE failed: Error: Resource
CREATE failed: Forbidden: Quota exceeded for instances: Requested 1, but
already used 4 of 4 instances (HTTP 403) (Request-ID:
req-02784ecc-4713-4601-84b5-099586d7b436)",
      "template_description" : "Creates an autoscaling application using
Ceilometer.",
      "timeout_mins" : null,
      "updated_time" : null
    } }


Whether "stack_status_reason" can satisfy your requirement?


Best Regards,
Liu, Hang(Henry)

----------------------------------------------------------
hangliu at cn.ibm.com | Tel: +8610-58748871   | ITN: 6-9058871
----------------------------------------------------------
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



Tao Tao <ttao at us.ibm.com> 写于 2014/11/07 08:08:17:

> From: Tao Tao <ttao at us.ibm.com>
> To: "OpenStack Development Mailing List \(not for usage questions\)"
> <openstack-dev at lists.openstack.org>
> Date: 2014/11/07 08:11
> Subject: Re: [openstack-dev] [heat] How to expose the error messages
> if the heat stack creation fails with software config/software deployment
>
> Hi, Ton:
>
> Thanks for your kind reply.
>
> What I really mean is how to expose the error messages so that I can
> use Heat REST API to find the error messages?
>
> In another word, how would a user to be able to find out the
> specific error message as a Heat client?
>
>
> Thanks,
> Tao Tao, Ph.D.
> IBM T. J. Watson Research Center
> 1101 Kitchawan Road
> Yorktown Heights, NY 10598
> Phone: (914) 945-4541
> Email: ttao at us.ibm.com
>
> [图像已删除] Ton Ngo---11/06/2014 07:04:30 PM---Hi Tao Tao,    If
> you use Ubuntu image, you can check /var/log/syslog
>
> From: Ton Ngo/Watson/IBM at IBMUS
> To: "OpenStack Development Mailing List \(not for usage questions\)"
> <openstack-dev at lists.openstack.org>
> Date: 11/06/2014 07:04 PM
> Subject: Re: [openstack-dev] [heat] How to expose the error messages
> if the heat stack creation fails with software config/software deployment
>
>
>
> Hi Tao Tao,
>   If you use Ubuntu image, you can check /var/log/syslog
> Look for section like:
> Running /opt/stack/os-config-refresh/configure.d/20-os-apply-config
> You should see the logs for running the script, error message, script
> output
> The scripts are stored on the VM instance
> in:  /var/lib/heat-config/heat-config-script
> Ton Ngo,
>
>
>
> From: Tao Tao/Watson/IBM at IBMUS
> To: "OpenStack List" <openstack-dev at lists.openstack.org>
> Date: 11/06/2014 12:09 PM
> Subject: [openstack-dev] [heat] How to expose the error messages if the
>            heat stack creation fails with software config/software
>            deployment
>
>
>
> Hi, All:
>
> When the heat stack creation fails due to software config/software
> deployment with scripts/chef/puppet, we are not able to locate the error
> message with Heat REST APIs.
>
> What is the best practice to solve this problem?
>
>
> Thanks,
> Tao Tao, Ph.D.
> IBM T. J. Watson Research Center
> 1101 Kitchawan Road
> Yorktown Heights, NY 10598
> Phone: (914) 945-4541
> Email: ttao at us.ibm.com_______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141107/9df091ba/attachment.html>