Bug 1221610

Summary:	RDO-manager beta fails to install: Deployment exited with non-zero status code: 6
Product:	[Community] RDO	Reporter:	Udi Kalifon <ukalifon>
Component:	openstack-tripleo	Assignee:	James Slagle <jslagle>
Status:	CLOSED EOL	QA Contact:	Shai Revivo <srevivo>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	trunk
Target Milestone:	---
Target Release:	Kilo
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-19 16:04:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Udi Kalifon 2015-05-14 12:43:24 UTC

Description of problem:
Deploying on CentOS 7.1 in a virtual environment with CentOS 7.1 guests, according to the test-day landing page: https://www.rdoproject.org/RDO-Manager_test_day_Kilo. Deployment of the overcloud fails when trying to deploy with either tuskar or heat. the resource that's failing is ControllerNodesPostDeployment:

ResourceUnknownStatus: Resource failed - Unknown status FAILED due to "Resource CREATE failed: ResourceUnknownStatus: Resource failed - Unknown status FAILED due to "Resource CREATE failed: Error: Deployment to server failed: deploy_status_code : Deployment exited with non-zero status code: 6""

No further info provided on the controller node in /var/log/messages so I don't know more about what's causing it to fail.


How reproducible:
100% 


Steps to Reproduce:
1. Work according to the instructions in the landing page, which point to http://docs.rdoproject.org/rdo-manager/master


Actual results:
Deployment of teh overcloud fails (the failing command is "instack-deploy-overcloud --tuskar")


Additional info:
The undercloud comes with Django 1.8, which is not supported. Not sure it it's related to this error or not, because I am not using the GUI at all.

Comment 3 Chandan Kumar 2016-05-19 16:04:23 UTC

This bug is against a Version which has reached End of Life.
If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.