Bug 1121749 - 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.
Summary: Rubygem-staypuft: we should let the user know that the deployment "fail" - ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rubygem-staypuft
Version: 5.0 (RHEL 7)
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
: Installer
Assignee: Mike Burns
QA Contact: Omri Hochman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-21 19:02 UTC by Leonid Natapov
Modified: 2014-09-23 15:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-09-23 15:20:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.