Red Hat Bugzilla – Bug 1297844
SPN should never run on the same host as the self hosted engine VM
Last modified: 2016-01-12 10:40:29 EST
Description of problem:
When the host the engine VM is running on is also the SPM host a crash of that host prevents any other host in the same cluster to spin up the engine VM as there is no SPM host.
This is lke a catch 22 situation where a new SPM host can't be selected because the engine VM is not running and the engine VM can not be started because the storage domains are down and can't be brought up without the SPM.
Version-Release number of selected component (if applicable):
Select the host the engine is running on as SPM and the power off that host.
Steps to Reproduce:
None of the other hosts can spin up the engine VM.
The fix would be to not allow the engine VM to run on the SPM host. Only time would be when there is a single host left in the cluster.
As soon there is a second host available the SPM role should be moved over to the host.
If the administrator migrate the engine VM to a host that is SPM the SPM role should move. The administrator should confirm that the SPM role will move before the migration start of the engine VM.
This is a duplicate of bug 1297845.
*** This bug has been marked as a duplicate of bug 1297845 ***