Red Hat Bugzilla – Bug 1278474
Adding hosts to wrong cluster results in deploy loop that you can't stop until you reboot engine
Last modified: 2016-02-10 14:14:33 EST
Created attachment 1090136 [details]
Host deploy log on the engine
Description of problem:
I tried to add a different arch of processor (AMD Phenom(tm) II X4 820 Processor) to a cluster that supported the AMD Opteron G1 and the whole host was installed and at the end of the install the host error:
First the host displayed: "Status of host kaitain was set to Up."
Second the host displayed: "Host kaitain is compatible with versions (3.0,3.1) and cannot join Cluster DC35Cluster which is set to version 3.5."
This cycled about every 3 seconds, it couldn't be stopped and it really bogged down the engine. The only way I could stop it was to reboot the RHEV-M engine.
Version-Release number of selected component (if applicable):
RHEL-6.7-20150811.1 & RHEV-M 3.6.0-17
Steps to Reproduce:
The host gets fully installed and hits a fail loop.
The host should not be installed and stopped as soon as RHEV-M knows it's not compatible.
host-deploy is ok.
please attach engine.log.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
This bug is not marked for z-stream, yet the milestone is for a z-stream version, therefore the milestone has been reset.
Please set the correct milestone or add the z-stream flag.
Created attachment 1090316 [details]
The scenario is the same as bug 1278474 : a host is being installed into incompatible cluster version.
*** This bug has been marked as a duplicate of bug 1279625 ***