Bug 1372549

Summary:	OSPD fails to delete stack for overcloud which is in failed state
Product:	Red Hat OpenStack	Reporter:	Feng Zhou <fezhou2>
Component:	rhosp-director	Assignee:	Angus Thomas <athomas>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Omri Hochman <ohochman>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	9.0 (Mitaka)	CC:	dbecker, fezhou2, mburns, morazi, rhel-osp-director-maint, sbaker, shardy, srevivo, zbitter
Target Milestone:	---
Target Release:	10.0 (Newton)
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-09-07 22:17: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:
Bug Depends On:
Bug Blocks:	1321607

Description Feng Zhou 2016-09-02 03:51:07 UTC

Description of problem:
  I created a overcloud with 3 controllers and 11 computes.   1 controller nodes failed creation,  and the cluster is in create_failed  status.

   Since it got stuck in this process for over an hour, we decided to delete the stack and recreate the cluster.  However,   "heat stack-delete cluster-name" failed,  and the cluster won't go away.  

  Repeated the commands 10 times,  still no luck.    Eventually,  we rebooted the OSP director node,  still stuck in same state.  Then we set the overcloud nodes (as shown by nova list) to "active" status manually,  and sent the "heat stack-delete" command again.  This seem to trigger another round of deletion which cleared the stack.

Version-Release number of selected component (if applicable):  OSPD 9


How reproducible:

Not tried to reproduce

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Zane Bitter 2016-09-02 13:40:01 UTC

*** Bug 1372548 has been marked as a duplicate of this bug. ***

Comment 3 Zane Bitter 2016-09-02 19:45:45 UTC

Without more information (e.g. heat-engine logs) it's impossible to say what the cause of this was and if the issue is actually in Heat or elsewhere.

Comment 4 Zane Bitter 2016-09-06 16:42:53 UTC

*** Bug 1372547 has been marked as a duplicate of this bug. ***

Comment 5 Feng Zhou 2016-09-07 21:47:30 UTC

Please close this one....     It happens rarely we don;t think it is important enough to spend time on right now