Ask Your Question
0

Resource CREATE failed: WaitConditionTimeout: 0 of 1 received

asked 2014-10-19 20:48:01 -0500

job gravatar image

Hi,

I'm doing some test with devstack icehouse, heat and AutoScalingMultiAZSample.template.

However, everytime I run the command: "heat stack-create demo -f AutoScalingMultiAZSample.template -P KeyName=heat_key", I get the following error for the event ElasticLoadBalancer ten minutes later: "Resource CREATE failed: WaitConditionTimeout: 0 of 1 received".

When i check the file Cloud-init.log, it seems stucked showing "/var/lib/heat-cfntools/cfn-userdata".

If I don't delete the stack after the error, 2 or 3 min aproimatly, the LB instance seems to send cnf-signal (checking -api-cfn.log) and cloud-init.log continue from /var/lib/heat-cfntools/cfn-userdata.

The template doesn't have any WaitHandler so I supposed it is a dafault. The only thing I've changed in the template was for it to use F20 cfntools image instead F17.

Any idea about how to approach this problem?

Thanks,

edit retag flag offensive close merge delete

1 answer

Sort by » oldest newest most voted
0

answered 2014-10-19 21:51:20 -0500

job gravatar image

I found where the default timeout for LoadBalancer was: “/opt/stack/heat/heat/engine/resources/loadbalancer.py”. I increased it to 1200 seconds, restart heat engine and the stack was able to finish.

For some reason unknown to me, the creation of the LoadBalancer and the script “/var/lib/heat-cfntools/cfn-userdata” was taking more time to complete than the default timeout of 600 in loadbalancer.py.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2014-10-19 20:40:47 -0500

Seen: 749 times

Last updated: Oct 19 '14