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 3Red 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.