Bug 1372828 - [RFE] Add automated power cycle on failed node deployment
Summary: [RFE] Add automated power cycle on failed node deployment
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: 9.0 (Mitaka)
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ---
: ---
Assignee: Angus Thomas
QA Contact: Omri Hochman
URL:
Whiteboard:
Depends On:
Blocks: 1321627
TreeView+ depends on / blocked
 
Reported: 2016-09-02 19:41 UTC by Feng Zhou
Modified: 2017-04-20 14:03 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-20 14:03:07 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Feng Zhou 2016-09-02 19:41:28 UTC 
Description of problem:

During the deployment of 3 controller + 10 computes,   1 controller got stuck in "spawning" status and never got rebooted/installed.  All other computes/controllers finished

I went to console and power cycled the server.  It was able to pick up from there and got installed.  The whole deployment finished with manual intervention.    However,   this is not desirable in automated operation environment for production.

Please make the reboots robust.

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


How reproducible:

Occasional

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 3 Red Hat Bugzilla Rules Engine 2017-03-08 08:28:34 UTC 
This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release.
Comment 7 Ramon Acedo 2017-04-20 14:03:07 UTC 
If this is still an issue, could you please log it with Red Hat Support for assessment of the issue please? Many thanks.
Note You need to log in before you can comment on or make changes to this bug.