Bug 1093044

Summary:	[Openstack-Staypuft]: When Deployment got stuck in progress there's no way to Remove it or to Retry again.
Product:	Red Hat OpenStack	Reporter:	Omri Hochman <ohochman>
Component:	rubygem-staypuft	Assignee:	Petr Chalupa <pchalupa>
Status:	CLOSED WONTFIX	QA Contact:	Omri Hochman <ohochman>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.0	CC:	aberezin, mburns, mlopes, morazi, mtaylor, pchalupa, rhos-maint, tsanders, yeylon
Target Milestone:	z4	Keywords:	TestOnly, ZStream
Target Release:	4.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	ruby193-rubygem-foreman-tasks-0.5.4-1	Doc Type:	Bug Fix
Doc Text:	Prior to this update, the foreman-tasks module did not correctly support cancellation of running tasks. Consequently, failed deployments would get stuck with no way of cancelling to restart; the deployment would need to be manually handled through a rails console. This fix adds a new cancellation option to foreman-tasks which allows users to cancel and restart tasks. The result is that users can now stop and restart Red Hat Enterprise Linux OpenStack Platform deployments when an invalid configuration is present.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-07-15 16:59:13 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:	1093126

Description Omri Hochman 2014-04-30 13:17:24 UTC

[Openstack-Staypuft]: When Deployment got stuck in progress there's no way to Remove it or to Retry again. 

Environment (Havana A4 puddle 2014-04-25.2):
---------------------------------------------
ruby193-rubygem-staypuft-0.0.11-5.el6ost.noarch
openstack-foreman-installer-1.0.6-2.el6ost.noarch
ruby193-rubygem-foreman_openstack_simplify-0.0.6-6.el6ost.noarch
openstack-puppet-modules-2013.2-9.el6ost.noarch
puppet-3.3.2-2.el6.noarch
puppet-server-3.3.2-2.el6.noarch
katello-installer-0.0.33-1.el6sat.noarch

Description:
-------------
When attempted to deploy openstack using Staypuft while the deployment was in progress 16% on the controller it got stuck with Error , there was no way to remove that deployment or starting over (Remove / Retry - missing buttons in this situation).

Comment 3 Omri Hochman 2014-04-30 18:48:46 UTC

Workaround: 
------------
- ssh to the foreman/staypuft server.
- run: 'foreman-rake console'.
- run (in the console) : 'ForemanTasks::Lock.where(name: 'deploy').destroy_all'

Comment 4 Martyn Taylor 2014-05-02 14:11:46 UTC

https://github.com/theforeman/staypuft/pull/110

Comment 5 Martyn Taylor 2014-05-15 10:26:03 UTC

The PR above needs updating to properly terminate tasks.  Right now it removes the lock but not the task.  We are currently waiting on support for this in Foreman via ForemanTasks.  Once this is in we should be OK to move foreward with the above PR.

Comment 6 Petr Chalupa 2014-05-15 11:49:28 UTC

This will be solved in and included in new version of ForemanTasks.

Comment 7 Petr Chalupa 2014-05-15 14:50:22 UTC

https://github.com/theforeman/foreman-tasks/pull/52

Comment 10 Omri Hochman 2014-05-27 21:04:35 UTC

Verified with : ruby193-rubygem-staypuft-0.0.16-1.el6ost.noarch

the "Force-Stop"  button - is providing the requested functionality and then it's possible to delete the stuck deployment.