On Tue, May 8, 2018 at 9:29 AM, Demeter Tibor <tdemeter@itsmart.hu> wrote:

Dear Listmember,

I've just upgrade to my ovirt-hosted-engine from 4.1 to 4.2.3. It was successful, but it saw "Data Center XYZ compatibility version is 4.1, which is lower than latest engine version 4.2. Please upgrade your Data Center to latest version to successfully finish upgrade of your setup."

My first question is that, it need to do BEFORE or AFTER the node upgrades?

I answer for the upgrade of DC/Cluster level. You can upgrade DC level when you have upgraded level of all its Clusters You can upgrade Cluster level when you have upgraded all its hosts More info here: https://www.ovirt.org/documentation/upgrade-guide/chap-Post-Upgrade_Tasks/ HIH, Gianluca

On 8 May 2018, at 09:29, Demeter Tibor <tdemeter@itsmart.hu> wrote: Dear Listmember, I've just upgrade to my ovirt-hosted-engine from 4.1 to 4.2.3. It was successful, but it saw "Data Center XYZ compatibility version is 4.1, which is lower than latest engine version 4.2. Please upgrade your Data Center to latest version to successfully finish upgrade of your setup." My first question is that, it need to do BEFORE or AFTER the node upgrades? I haven't upgrade my nodes yet, because after upgrade the live migration does not work with some VMs. It seems only affected those VMs that's have big (>8GB ) memory. It counting to 99 percent and after a while just stopped. Did you try other migration policies? At this moment I can't stop my affected, productive VMs, so I can't do the upgrade of nodes. They’re probably too active. Maybe you can stop some services inside those guests? Migrate when they are not that busy? I just wondering, if i do the upgrade to 4.2 , that's maybe repair my the live migration function? What can I do? Centos 7.4, NFS storage, 4 nodes, Hyperconverged hosted engine. Thanks in advance, Tibor _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org