After introducing cluster emulation mode feature(bug 927874) we reset/nullify the auto detected value on every Edit Cluster dialog opening. We should only do that on a cluster compatibility level change
Can you provide some info on how to test this?
Most simple would be that you have a 3.2 cluster with an up host and a down VM. Try to edit some property on the cluster (not the version) and try to run that VM. It should correctly start up. If it fails it means that the emulated machine field is nullified (e.g. emulated_machine field on vds_groups table is null). Than stop this VM and try to change the version of the cluster to 3.3 (this should change also the emulated_machine field on vds_groups table according to the host but NOT to null). So try to run the VM and it should still work.
verified in is15
Closing - RHEV 3.3 Released