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

Hi Steven, Thanks for answering, I saw lot of errors in /var/log/cloud-init.log: http://paste.fedoraproject.org/118898/56463661/ I think this fedora19 is using an old outdated version of openshift that doesn't work anymore, did you know where to find an updated heat template or a good howto using the centos6.5 templates? Thanks in advanced, ------------------ Antonio C. Velez Baez Linux Consultant Vidalinux.com RHCE, RHCI, RHCX, RHCOE Red Hat Certified Training Center Email: acvelez(a)vidalinux.com Tel: 1-787-439-2983 Skype: vidalinuxpr Twitter: @vidalinux.com Website: www.vidalinux.com ----- Original Message ----- From: "Steven Hardy" <shardy(a)redhat.com&gt; To: "Antonio C. Velez" <acvelez(a)vidalinux.com&gt; Cc: rdo-list(a)redhat.com Sent: Thursday, July 17, 2014 7:05:54 AM Subject: Re: [Rdo-list] Openshift-Origin via Heat Icehouse Fedora20 | BrokerWaitCondition | AWS::CloudFormation::WaitCondition | CREATE_FAILED On Thu, Jul 17, 2014 at 05:36:59AM -0400, Antonio C. Velez wrote: 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 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.