Bug 1372546 - Overcloud stack deletion failed and all nodes get stuck in "deleting" status
Summary: Overcloud stack deletion failed and all nodes get stuck in "deleting" status
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: 9.0 (Mitaka)
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: ---
Assignee: Angus Thomas
QA Contact: Omri Hochman
URL:
Whiteboard:
Depends On:
Blocks: 1321607
TreeView+ depends on / blocked
 
Reported: 2016-09-02 03:44 UTC by Feng Zhou
Modified: 2017-10-12 14:26 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-12 14:26:33 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Feng Zhou 2016-09-02 03:44:05 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 3 Red Hat Bugzilla Rules Engine 2017-06-04 02:58:49 UTC
This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release.

Comment 4 Zane Bitter 2017-10-12 14:26:33 UTC
It's impossible to know what happened here without seeing the reason the stack failed and the status of the resources in Nova. I'm going to close this on the assumption that this information is no longer available, but please do reopen if you see it again or have more data.


Note You need to log in before you can comment on or make changes to this bug.