[Rdo-list] Openshift-Origin via Heat Icehouse Fedora20 | BrokerWaitCondition | AWS::CloudFormation::WaitCondition | CREATE_FAILED

Steven Hardy shardy at redhat.com
Thu Jul 17 11:05:54 UTC 2014


On Thu, Jul 17, 2014 at 05:36:59AM -0400, Antonio C. Velez wrote:
> Hi everyone,
> 
> I'm trying to build openshift-origin using heat template: https://github.com/openstack/heat-templates/tree/master/openshift-origin/F19 the BrokerFlavor complete without issues, but stops giving the following error:
> 
> 2014-07-17 04:17:50.266 6759 INFO heat.engine.resource [-] creating WaitCondition "BrokerWaitCondition" Stack "openshift" [d9c72c56-8d90-47fe-9036-084146eeb175]
> 2014-07-17 05:16:28.484 6759 INFO heat.engine.scheduler [-] Task stack_task from Stack "openshift" [d9c72c56-8d90-47fe-9036-084146eeb175] timed out
> 2014-07-17 05:16:28.704 6759 WARNING heat.engine.service [-] Stack create failed, status FAILED
> 
> I tried increasing the BrokerWaitCondition timeout but doesn't help.

Please check the following:
1. heat_waitcondition_server_url is set correctly in your
  /etc/heat/heat.conf:

heat_waitcondition_server_url = http://192.168.0.6:8000/v1/waitcondition

Here 192.168.0.6 needs to be the IP address of the box running
heat-api-cfn, and it must be accessible to the instance.

Relatedly, the heat-api-cfn service must be installed and running, which
means setting the -os-heat-cfn-install/OS_HEAT_CFN_INSTALL option if you
installed via packstack.

2. Ensure no firewalls are blocking access
  - SSH to the instance
  - Install nmap inside the instance
  - nmap 192.168.0.6 (using the above URL as an example)
  - Port tcp/8000 should be open

3. Ensure the instances can connect to the internet
  - Should be covered by installing nmap above, but if your network
    configuration is broken and they can't connect to the internet, the
    install of packages will hang up and the WaitCondition will time out.

If all of the above is OK, log on to the instance during the install via
SSH and tail /var/log/cloud-init*, looking for errors or a point in the
install where it is getting stuck.

Also, I assume the image you're using has been prepared as per the
instructions in the README.rst?

Hope that helps.

--
Steve Hardy
Red Hat Engineering, Cloud




More information about the dev mailing list