Description of problem: After incorrectly adding a ppc64 host in an empty x86-64 cluster and removing it, the cluster cannot accept new x86-64 hosts, accusing incompatibility between the emulatedMachines property of the cluster and the hosts being added. Version-Release number of selected component (if applicable): 3.4 How reproducible: Always Steps to Reproduce: 1. Create a cluster with any x86-64 processor name 2. Add a ppc64 host into it 3. Remove this ppc64 host 4. Add a x86-64 host Actual results: The x86-64 host won't be added into the cluster, resulting in an error due to the emulatedMachines property of the cluster being incorrectly set. Expected results: The x86-64 host is added into the cluster. Additional info: This bug also occurs in other cases where the HandleVdsCpuFlagsOrClusterChangedCommand sets a host an non-operational but the emulatedMachines property of this host is used to populate the same field in the cluster, enven if the host was reject.
Setting target release to current version for consideration and review. please do not push non-RFE bugs to an undefined target release to make sure bugs are reviewed for relevancy, fix, closure, etc.
i think this was already solved by http://gerrit.ovirt.org/#/c/27539 can you please verify problem solved?
emulated machine config value should be tight to architecture. this will be easier to manage and it won't be coupled with where you invoke it in the code x86_64 {rhel6.5, pc}, ppc {pseries} same as we did with other cross architecure config values
fix was reverted and have some issues, moving to 3.5.2
Re-targeting to 3.5.3 since this bug has not been marked as blocker for 3.5.2 and we have already released 3.5.2 Release Candidate.
would be nice to clear the machine type when last host is removed from the cluster
The machine type can be cleared by right-clicking the cluster row, pressing "Reset Emulated Machine" and confirming the operation. Because of this functionality, implicit machine type reset is not needed.