Steve,
Nevermind, I fix the issue, I was calling the same port for OpenShiftNode, changing this
got it working.
Thanks!
------------------
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: "Antonio C. Velez" <acvelez(a)vidalinux.com>
To: "Steven Hardy" <shardy(a)redhat.com>
Cc: rdo-list(a)redhat.com
Sent: Friday, July 18, 2014 5:22:01 AM
Subject: Re: [Rdo-list] Openshift-Origin via Heat Icehouse Fedora20 | BrokerWaitCondition
| AWS::CloudFormation::WaitCondition | CREATE_FAILED
Steven,
I manage to understand centos6.5 templates and get it to work, then now I got another
error,
2014-07-18 04:47:26.117 6759 ERROR heat.engine.resource [-] CREATE : Server
"OpenShiftNode" Stack "openshift"
[2d5caea3-ca3e-47f1-92e0-898109d671dd]
2014-07-18 04:47:26.117 6759 TRACE heat.engine.resource Traceback (most recent call
last):
2014-07-18 04:47:26.117 6759 TRACE heat.engine.resource File
"/usr/lib/python2.7/site-packages/heat/engine/resource.py", line 417, in
_do_action
2014-07-18 04:47:26.117 6759 TRACE heat.engine.resource handle())
2014-07-18 04:47:26.117 6759 TRACE heat.engine.resource File
"/usr/lib/python2.7/site-packages/heat/engine/resources/server.py", line 535, in
handle_create
2014-07-18 04:47:26.117 6759 TRACE heat.engine.resource admin_pass=admin_pass)
2014-07-18 04:47:26.117 6759 TRACE heat.engine.resource File
"/usr/lib/python2.7/site-packages/novaclient/v1_1/servers.py", line 871, in
create
2014-07-18 04:47:26.117 6759 TRACE heat.engine.resource **boot_kwargs)
2014-07-18 04:47:26.117 6759 TRACE heat.engine.resource File
"/usr/lib/python2.7/site-packages/novaclient/v1_1/servers.py", line 534, in
_boot
2014-07-18 04:47:26.117 6759 TRACE heat.engine.resource return_raw=return_raw,
**kwargs)
2014-07-18 04:47:26.117 6759 TRACE heat.engine.resource File
"/usr/lib/python2.7/site-packages/novaclient/base.py", line 152, in _create
2014-07-18 04:47:26.117 6759 TRACE heat.engine.resource _resp, body =
self.api.client.post(url, body=body)
2014-07-18 04:47:26.117 6759 TRACE heat.engine.resource File
"/usr/lib/python2.7/site-packages/novaclient/client.py", line 312, in post
2014-07-18 04:47:26.117 6759 TRACE heat.engine.resource return self._cs_request(url,
'POST', **kwargs)
2014-07-18 04:47:26.117 6759 TRACE heat.engine.resource File
"/usr/lib/python2.7/site-packages/novaclient/client.py", line 286, in
_cs_request
2014-07-18 04:47:26.117 6759 TRACE heat.engine.resource **kwargs)
2014-07-18 04:47:26.117 6759 TRACE heat.engine.resource File
"/usr/lib/python2.7/site-packages/novaclient/client.py", line 268, in
_time_request
2014-07-18 04:47:26.117 6759 TRACE heat.engine.resource resp, body = self.request(url,
method, **kwargs)
2014-07-18 04:47:26.117 6759 TRACE heat.engine.resource File
"/usr/lib/python2.7/site-packages/novaclient/client.py", line 262, in request
2014-07-18 04:47:26.117 6759 TRACE heat.engine.resource raise
exceptions.from_response(resp, body, url, method)
2014-07-18 04:47:26.117 6759 TRACE heat.engine.resource Conflict: Port
9bceb816-93f4-4d72-8ae8-de8e5758bd6d is still in use. (HTTP 409) (Request-ID:
req-685b5295-4918-417d-894d-d416bf9e7b1c)
2014-07-18 04:47:26.117 6759 TRACE heat.engine.resource
2014-07-18 04:47:26.848 6759 WARNING heat.engine.service [-] Stack create failed, status
FAILED
Any advice? Thanks!
------------------
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>
To: "Antonio C. Velez" <acvelez(a)vidalinux.com>
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:
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
--
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.