Bug 1128361

Summary:	HA: Failure to start 'openstack-heat-api-cfn-clone' leads to HA deployment get paused at 60%.
Product:	Red Hat OpenStack	Reporter:	Leonid Natapov <lnatapov>
Component:	openstack-foreman-installer	Assignee:	Brad P. Crochet <brad>
Status:	CLOSED ERRATA	QA Contact:	Leonid Natapov <lnatapov>
Severity:	high	Docs Contact:
Priority:	high
Version:	5.0 (RHEL 7)	CC:	aberezin, brad, jguiditt, mburns, morazi, ohochman, rhos-maint, yeylon
Target Milestone:	ga
Target Release:	Installer
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-foreman-installer-2.0.20-1.el6ost	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-08-21 18:08:37 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 Leonid Natapov 2014-08-09 13:56:07 UTC

HA: Failure to start 'openstack-heat-api-cfn-clone' leads to  HA deployment get paused at 60%.  Need to "resume" in order to complete deployment.

HA controller deployment stopped at 60% complaining on puppet error.
The only error I can see in puppet log was the error bellow:
Deployment got stuck on 60%. After manually resuming the deployment it finished successfully.

change from notrun to 0 failed: /usr/sbin/pcs constraint order start openstack-heat-api-clone then start openstack-heat-api-cfn-clone returned 1 instead of one of [0]

/usr/sbin/pcs constraint order start openstack-heat-api-clone then start openstack-heat-api-cfn-clone returned 1 instead of one of [0]

Error: Resource 'openstack-heat-api-cfn-clone' does not exist

Comment 2 Brad P. Crochet 2014-08-13 18:04:33 UTC

PR submitted:

https://github.com/redhat-openstack/astapor/pull/352

Comment 3 Jason Guiditta 2014-08-13 19:54:59 UTC

Merged

Comment 6 Leonid Natapov 2014-08-18 09:10:59 UTC

Can't reproduce on openstack-foreman-installer-2.0.20-1.el6ost

Comment 7 errata-xmlrpc 2014-08-21 18:08:37 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-1090.html