Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1180250

Summary: rubygem-staypuft: Cancelling a deployment in progress by clicking on "Force unlock" doesn't work on first attempt.
Product: Red Hat OpenStack Reporter: Alexander Chuzhoy <sasha>
Component: rubygem-staypuftAssignee: Mike Burns <mburns>
Status: CLOSED WONTFIX QA Contact: Omri Hochman <ohochman>
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: mburns, yeylon
Target Milestone: ---Keywords: ZStream
Target Release: Installer   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-04-29 14:49:30 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:
Bug Depends On:    
Bug Blocks: 1177026    
Attachments:
Description Flags
staypuft machine /etc and logs none

Description Alexander Chuzhoy 2015-01-08 17:26:21 UTC 
rubygem-staypuft: Cancelling a deployment in progress by clicking on "Force unlock" doesn't work on first attempt.

Environment:
ruby193-rubygem-foreman_openstack_simplify-0.0.6-8.el7ost.noarch
openstack-foreman-installer-3.0.8-1.el7ost.noarch
ruby193-rubygem-staypuft-0.5.9-1.el7ost.noarch
rhel-osp-installer-client-0.5.4-1.el7ost.noarch
openstack-puppet-modules-2014.2.8-1.el7ost.noarch
rhel-osp-installer-0.5.4-1.el7ost.noarch


Steps to reproduce:
1. Install rhel-osp-installer.
2. Start a deployment.
3. Go to the "Overview" tab of the deployment.
4. Click on "show more details".
5. Click on "Force unlock".
6. Delete all hosts participated in the deployment.
7. Go back to the deployment.

Result:
In the majority of cases you'll see that the deployment is "paused with errors" - the progress bar is marked red.
So you'll have to click on "Force unlock" again.

Expected result:
The deployment shouldn't be paused with errors. It should state "Not deployed, yet."  - like it is after the second time I click on "Force unlock.
Comment 1 Alexander Chuzhoy 2015-01-08 17:34:27 UTC 
Created attachment 977860 [details]
staypuft machine /etc and logs