Description of problem: Today I've got a case from customer who was using RHEV-M 3.4 and RHEL/RHEV 6.5 hypervisors , after upgrading Manager to 3.5 and changing compatibility mode to 3.5 for both Datacenter and Cluster customer was unable to activate the hypervisors anymore until he upgraded them too as per https://access.redhat.com/solutions/463903 Shouldn't RHEV Manager warn the customer at the stage where he's trying to change compatibility mode that Datacenter/Cluster contains hypervisor which are not compatible with the mode being set? This would help to prevent the issues like in the case that I had. Please let me know if that's possible and makes any sense in your opinion. -- Kind Regards, Igor Netkachev Technical Support Engineer Red Hat Global Support Services
Before allowing you to change a cluster level, we do check that all hosts are compatible with this cluster level. What was the exact versions of engine+VDSM the customer worked with? In case of node, what was the image version?
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days