Bug 1347011

Summary: [Heat] Unable to delete a deployment in progress: "ERROR: Stack overcloud already has an action (CREATE) in progress."
Product: Red Hat OpenStack Reporter: Alexander Chuzhoy <sasha>
Component: openstack-heatAssignee: Zane Bitter <zbitter>
Status: CLOSED DUPLICATE QA Contact: Amit Ugol <augol>
Severity: medium Docs Contact:
Priority: medium    
Version: 9.0 (Mitaka)CC: jason.dobies, jcoufal, mburns, rhel-osp-director-maint, sbaker, shardy, srevivo, tvignaud
Target Milestone: ---Keywords: Triaged
Target Release: 11.0 (Ocata)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-20 13:52:08 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 Alexander Chuzhoy 2016-06-15 19:24:29 UTC
openstack-heat: Unable to delete a deployment in progress: "ERROR: Stack overcloud already has an action (CREATE) in progress."


Environment:
openstack-heat-api-6.0.0-4.el7ost.noarch
instack-undercloud-4.0.0-2.el7ost.noarch
openstack-heat-common-6.0.0-4.el7ost.noarch
python-heatclient-1.2.0-1.el7ost.noarch
openstack-heat-engine-6.0.0-4.el7ost.noarch
openstack-tripleo-heat-templates-2.0.0-9.el7ost.noarch

Steps to reproduce:
1. Start an overcloud deployment.
2. While the deployment is in progress atemmpt to delete the overcloud deployment with:
 openstack stack delete --yes overcloud

Result:
ERROR: Stack overcloud already has an action (CREATE) in progress

Expected result:
The deployment in progress should be deleted. The user/admin shouldn't wait until the running deployment finishes to reinstall.

Comment 3 Alexander Chuzhoy 2016-09-12 16:17:08 UTC
Environment:
openstack-heat-api-cfn-7.0.0-0.20160823082523.1106458.el7ost.noarch
openstack-heat-templates-0.0.1-0.20160822094546.1ac2823.el7ost.noarch
openstack-heat-engine-7.0.0-0.20160823082523.1106458.el7ost.noarch
instack-undercloud-5.0.0-0.20160818065636.41ef775.el7ost.noarch
openstack-heat-common-7.0.0-0.20160823082523.1106458.el7ost.noarch
openstack-heat-api-7.0.0-0.20160823082523.1106458.el7ost.noarch
openstack-tripleo-heat-templates-5.0.0-0.20160823140311.72404b.1.el7ost.noarch


was able to initiate stack deletion of a stack being created.

Comment 4 Zane Bitter 2016-10-20 13:52:08 UTC
This was due to the timeout on the stack stop message being far too low (2s). This will be fixed in OSP9 by bug 1384667, and is already fixed upstream in Newton (OSP10).

In the meantime, you can work around this by setting the config option "engine_life_check_timeout" to a larger value (e.g. 30s).

*** This bug has been marked as a duplicate of bug 1384667 ***