Ask Your Question

jrichards99's profile - activity

2017-10-16 08:05:48 -0500 received badge  Nice Question (source)
2016-02-29 02:18:09 -0500 received badge  Famous Question (source)
2016-02-04 22:58:54 -0500 received badge  Notable Question (source)
2016-02-04 02:22:13 -0500 received badge  Popular Question (source)
2015-10-24 22:12:01 -0500 received badge  Famous Question (source)
2015-10-17 14:55:21 -0500 received badge  Student (source)
2015-10-09 09:05:30 -0500 received badge  Notable Question (source)
2015-10-08 00:07:25 -0500 received badge  Popular Question (source)
2015-10-07 09:00:10 -0500 asked a question Heat stack create failed

Trying to stand up a cloud using tripleO on CentOS 7 with libvirt+kvm virtual machines. Following along the tripleO documentation just to get something stood up for learning purposes, so using all the default options. Seems I am almost there. The overcloud deploy does not complete successfully:

[stack@instack ~]$ openstack overcloud deploy --templates
Deploying templates in the directory /usr/share/openstack-tripleo-heat-templates
Stack failed with status: Resource CREATE failed: resources.ComputePuppetDeployment: resources.ComputeNodesPostDeployment.Error: resources[0]: Deployment to server failed: deploy_status_code: Deployment exited with non-zero status code: 1
Heat Stack create failed.
[stack@instack ~]$ nova list
+--------------------------------------+-------------------------+--------+------------+-------------+--------------------+
| ID                                   | Name                    | Status | Task State | Power State | Networks           |
+--------------------------------------+-------------------------+--------+------------+-------------+--------------------+
| e7d6a686-200a-4e44-8c30-da4678009e17 | overcloud-controller-0  | ACTIVE | -          | Running     | ctlplane=192.0.2.9 |
| 07a70b9c-83ad-49b6-ba1d-c858ddeea7e7 | overcloud-novacompute-0 | ACTIVE | -          | Running     | ctlplane=192.0.2.8 |
+--------------------------------------+-------------------------+--------+------------+-------------+--------------------+
[stack@instack ~]$ heat stack-list
+--------------------------------------+------------+---------------+---------------------+---------------------+
| id                                   | stack_name | stack_status  | creation_time       | updated_time        |
+--------------------------------------+------------+---------------+---------------------+---------------------+
| 285d7d66-d15b-4dd2-ac7b-c4e0db0d6ef5 | overcloud  | UPDATE_FAILED | 2015-10-06T17:32:05 | 2015-10-06T18:18:59 |
+--------------------------------------+------------+---------------+---------------------+---------------------+

Here is a piece of the heat-engine.log:

2015-10-06 17:41:37.664 22052 ERROR heat.engine.resources.openstack.heat.software_deployment [-] Deployment to server failed: deploy_status_code : Deployment exited with non-zero status code: 1
2015-10-06 17:41:37.664 22052 INFO heat.engine.resource [-] CREATE: StructuredDeployment "0" [55e4574d-d8d2-48d0-ae6f-0fa42ba92e1a] Stack "overcloud-ComputeNodesPostDeployment-a3ulpbr3lhra-ComputePuppetDeployment-g56x63ubizqh" [c3d3ff24-c09e-49de-9efe-1b8c2e175dfc]
2015-10-06 17:41:37.664 22052 ERROR heat.engine.resource Traceback (most recent call last):
2015-10-06 17:41:37.664 22052 ERROR heat.engine.resource   File "/usr/lib/python2.7/site-packages/heat/engine/resource.py", line 612, in _action_recorder
2015-10-06 17:41:37.664 22052 ERROR heat.engine.resource     yield
2015-10-06 17:41:37.664 22052 ERROR heat.engine.resource   File "/usr/lib/python2.7/site-packages/heat/engine/resource.py", line 682, in _do_action
2015-10-06 17:41:37.664 22052 ERROR heat.engine.resource     yield self.action_handler_task(action, args=handler_args)
2015-10-06 17:41:37.664 22052 ERROR heat.engine.resource   File "/usr/lib/python2.7/site-packages/heat/engine/scheduler.py", line 309, in wrapper
2015-10-06 17:41:37.664 22052 ERROR heat.engine.resource     step = next(subtask)
2015-10-06 17:41:37.664 22052 ERROR heat.engine.resource   File "/usr/lib/python2.7/site-packages/heat/engine/resource.py", line 656, in action_handler_task
2015-10-06 17:41:37.664 22052 ERROR heat.engine.resource     while not check(handler_data):
2015-10-06 17:41:37.664 22052 ERROR heat.engine.resource   File "/usr/lib/python2.7/site-packages/heat/engine/resources/openstack/heat/software_deployment.py", line 443, in check_create_complete
2015-10-06 17:41:37.664 22052 ERROR heat.engine.resource     return self._check_complete()
2015-10-06 17:41:37.664 22052 ERROR heat.engine.resource   File "/usr/lib/python2.7/site-packages/heat/engine/resources/openstack/heat/software_deployment.py", line 293, in _check_complete
2015-10-06 17:41:37.664 22052 ERROR heat.engine.resource     raise exc
2015-10-06 17:41:37.664 22052 ERROR heat.engine.resource Error: Deployment to server failed: deploy_status_code : Deployment exited with non-zero status code: 1
2015-10-06 17:41:37.664 22052 ERROR heat.engine.resource

Any tips on where I can start debugging this issue or proceed from here? Is the non-zero status code actually coming from the overcloud machines somewhere and I need to dig there?

Edit ... (more)

2015-10-07 00:25:01 -0500 asked a question openstack baremetal introspection internal server error

Using tripleO going through the documented process step by step with VMs on a CentOS7 system failed on introspection on the undercloud VM. I traced it down to a bad database connection string in /etc/ironic-inspector/inspector.conf , the database connection string was:

connection = sqlite:///var/lib/ironic-inspector/inspector.sqlite

Which is a relative path. Changed it to connection = sqlite:////var/lib/ironic-inspector/inspector.sqlite (absolute path), migrated the database and it now works.

I'm not sure if I did something wrong, or if there is a bug somewhere, or whether the bug is in tripleO or upstream OpenStack (I just started with OpenStack last week and am still climbing the learning curve), so thought I would post it here in case anyone was interested and can file an appropriate bug report or suggest where I may have gone wrong.