Bug 1121749

Summary:	Rubygem-staypuft: we should let the user know that the deployment "fail" - there is no reason to leave the deployment stuck on 60% in case of puppet error.
Product:	Red Hat OpenStack	Reporter:	Leonid Natapov <lnatapov>
Component:	rubygem-staypuft	Assignee:	Mike Burns <mburns>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Omri Hochman <ohochman>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	5.0 (RHEL 7)	CC:	mburns
Target Milestone:	---
Target Release:	Installer
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-09-23 15:20:39 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-07-21 19:02:50 UTC

Rubygem-staypuft: we should let the user know that the deployment "fail"  -  there is no reason to leave the deployment stuck on 60%  in case of puppet error.

Now the deployment get stuck on 60% with the "paused' status.

Comment 1 Leonid Natapov 2014-07-21 19:05:07 UTC

rhel-osp-installer-0.1.1-1.el6ost.noarch
openstack-foreman-installer-2.0.15-1.el6ost.noarch
ruby193-rubygem-foreman_openstack_simplify-0.0.6-8.el6ost.noarch
openstack-puppet-modules-2014.1-19.1.el6ost.noarch

Comment 3 Mike Burns 2014-09-23 15:20:39 UTC

We should be preventing fails at 60% in general, but I think in most cases that we fail correctly now.

Comment 4 Mike Burns 2014-09-23 15:28:10 UTC

Please reopen if you think this is still a problem with specific details.