Description of problem: If the Cluster Version was only upgraded and the Data Center version is still using old version then the "Edit Cluster" will shows the "Data center" version as a default form field for "Compatibility Version". One has to manually change the cluster compatibility everytime to make a change or to save the form. Version-Release number of selected component (if applicable): Red Hat Enterprise Virtualization 3.5 How reproducible: 100% Steps to Reproduce: 1. Create a data center and cluster of version 3.4 2. Upgrade the cluster version to 3.5 3. Try to edit the cluster and can see that the default compatibility version is 3.4 . We need to manually change this to 3.5 for saving the form. Actual results: Cluster compatibility version is showing incorrect value in "Edit Cluster". Expected results: Cluster compatibility version should show the correct value. Additional info:
Hi Do you mean that you have 3.4 hosts in a 3.4 cluster in a 3.4 DC and now you had upgraded all the hosts that belongs to the 3.4 cluster to 3.5 and you expect now that the edit dialog on that cluster will show 3.5 as the comparability version ???
(In reply to Eli Mesika from comment #1) > Hi > > Do you mean that you have 3.4 hosts in a 3.4 cluster in a 3.4 DC and now you > had upgraded all the hosts that belongs to the 3.4 cluster to 3.5 and you > expect now that the edit dialog on that cluster will show 3.5 as the > comparability version ??? Yes, When we upgrade the 3.4 cluster version to 3.5 and if the Data Center version is still in 3.4, the edit cluster button is now showing as 3.4.
(In reply to nijin ashok from comment #2) Hi again In that case it is functioning as designed. The comparability version is on the engine side logic and is not reported from VDSM , also, the Cluster itself is a logical entity on the engine side while in VDSM side we are aware only to the Host as an entity. Due to that, I recommend to close this as NOTABUG