Dear oVirt Support, Description of problem: I can't upgrade the Cluster Compatibility Version from 3.5 to 3.6. I get this message: Error while executing action: Cannot update Data Center compatibility version to a value that is greater than its Cluster's version. The following clusters should be upgraded Fram1. And this is the information is the engine.log ERROR_CANNOT_UPDATE_STORAGE_POOL_COMPATIBILITY_VERSION_BIGGER_THAN_CLUSTERS Version-Release number of selected component (if applicable): Ovirt engine: oVirt Engine Version: 3.6.7.5-1.el6 OS: CentOS release 6.8 (Final) vdsm: vdsm-4.16.27-0.el6.x86_64 Best Regards, Sandor Kalmanczi
(In reply to Csiga from comment #0) > Dear oVirt Support, > > Description of problem: > > I can't upgrade the Cluster Compatibility Version from 3.5 to 3.6. > > I get this message: Error while executing action: Cannot update Data Center > compatibility version to a value that is greater than its Cluster's version. > The following clusters should be upgraded Fram1. So, did you try updating cluster "Fram1" to 3.6? > > And this is the information is the engine.log > > ERROR_CANNOT_UPDATE_STORAGE_POOL_COMPATIBILITY_VERSION_BIGGER_THAN_CLUSTERS > > Version-Release number of selected component (if applicable): > > Ovirt engine: oVirt Engine Version: 3.6.7.5-1.el6 > OS: CentOS release 6.8 (Final) > vdsm: vdsm-4.16.27-0.el6.x86_64 > > Best Regards, > Sandor Kalmanczi
Created attachment 1200498 [details] where1
Created attachment 1200500 [details] where2
Created attachment 1200501 [details] where3
is the Dataplex-Farm1 the only cluster in that datacenter? Because if not, all the clusters of the datacenter have to be updated to 3.6 before the datacenter itself can be updated.
Created attachment 1202324 [details] Datac show 1
Created attachment 1202325 [details] Datac show 1
Dear Tomas Jelinek, Yes this is the only cluster this datacenter. I attached screenshoots. Besz Regards, Sandor Kalmanczi
I have a suspicion that the "default" cluster may cause the issue. Could you please check if it is set to 3.6 before updating the datacenter? Also please attach the engine.log thank you
Created attachment 1202804 [details] Engine's logs
Dear Tomas Jelinek, I attached the engine.log Best Regards, Sandor Kalmanczi
So, I was looking at your screenshots again and I have realized that: - in "where1" the cluster compatibility is not updated, it is marked red. - in "Datac show 1" I see the cluster compatiblity is 3.5 - e.g. the datacenter will not be updatable. So, the problem is no that you can not update the datacenter but the fact you can not update the cluster. If you point your mouse to the cluster compatibility version in edit cluster dialog, it should tell you what he does not like.
Created attachment 1202874 [details] Trying upgrade 1
Created attachment 1202876 [details] Trying upgrade 2
Created attachment 1202877 [details] Trying upgrade 3
Created attachment 1202878 [details] Trying upgrade 1-2-3 engine.log
Dear Tomas Jelinek, I was trying the cluster update again. I have attached the engine log and the screens of the fail. Best Regards, Sandor Kalmanczi
There is nothing in the engine.log since the frontend validation has stopped you. So I need to see the title - just point the mouse over the red square over the custom compatibility version. But anyway, I think you have at least 1 VM in that cluster which is not down. This was a limitation in 3.6.7, it has been removed in 3.6.8. Please try to either shut all the VMs down and than update the cluster version or update the engine to 3.6.8 and than you should be able to update the cluster compatibility version also with running VMs.
sorry, my bad, there is no such thing as ovirt-3.6.8. So, what you need to do is to schedule a maintenance window, turn all the VMs in the cluster off, update cluster compatibility and than turn the VMs back on. After this you will be able to update also the datacenter.
Based on the logs and discussion I conclude that: - in 3.6.7 you need to schedule a maintenance window, turn all VMs off, update cluster level and than you can update the DC level - in 4.0 you don't need to turn the VMs off, they will be marked as next run snapshot and reconfigured to work on older compatiblity until re-started Consequently, closing as not-a-bug. If you feel there is indeed an issue in the flow I have explained above, please feel free to reopen.
Dear Support, We was extreme busy, Thank you for your help. We will try to upgrade the cluster 4.x. Best Regards, Sandor Kalmanczi