Bug 1372828

Summary:	[RFE] Add automated power cycle on failed node deployment
Product:	Red Hat OpenStack	Reporter:	Feng Zhou <fezhou2>
Component:	rhosp-director	Assignee:	Angus Thomas <athomas>
Status:	CLOSED NOTABUG	QA Contact:	Omri Hochman <ohochman>
Severity:	high	Docs Contact:
Priority:	low
Version:	9.0 (Mitaka)	CC:	dbecker, dtantsur, jcoufal, jdonohue, mburns, morazi, racedoro, rhel-osp-director-maint, sbaker, shardy, srevivo
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
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:	2017-04-20 14:03:07 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:	1321627

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.