
Hi, I'm in the process of upgrading to 4.1 from 3.6.7 (centos 6) The default cluster runs in 3.5 compatibility mode. I cannot add a new Centos 7 host: 2017-10-23 13:50:08,359 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-40) [6a0dd9df] Correlation ID: 6a0dd9df, Job ID: e570c94b-bbd8-486b-bb93-3d28fb905bb3, Call Stack: null, Custom Event ID: -1, Message: Host v5 is compatible with versions (3.6,4.0,4.1) and cannot join Cluster Default which is set to version 3.5. I'm following https://www.ovirt.org/feature/inclusterupgrade/ for upgrading. I've set engine-config -s CheckMixedRhelVersions=false --cver=3.5 restarted and set Scheduling policy InClusterUpgrade Any recommendations how to proceed without shutting down all VMs? I also want to avoid creating a new cluster with 3.6 version cause then I will have to shutdown all VMs again. Thanks G ps. The steps I had in mind were: upgrade serially hosts to Centos 7 migrate VMs there backup-restore engine to new Centos 7 machine

On 23 Oct 2017, at 12:57, Kapetanakis Giannis <bilias@edu.physics.uoc.gr> wrote:
Hi,
I'm in the process of upgrading to 4.1 from 3.6.7 (centos 6) The default cluster runs in 3.5 compatibility mode.
I cannot add a new Centos 7 host: 2017-10-23 13:50:08,359 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-40) [6a0dd9df] Correlation ID: 6a0dd9df, Job ID: e570c94b-bbd8-486b-bb93-3d28fb905bb3, Call Stack: null, Custom Event ID: -1, Message: Host v5 is compatible with versions (3.6,4.0,4.1) and cannot join Cluster Default which is set to version 3.5.
I'm following https://www.ovirt.org/feature/inclusterupgrade/ for upgrading.
I've set engine-config -s CheckMixedRhelVersions=false --cver=3.5 restarted and set Scheduling policy InClusterUpgrade
Any recommendations how to proceed without shutting down all VMs?
while you are still in 3.6 engine you need to upgrade that Default cluster to 3.6. This requires VMs power cycle to fully update everything. only then upgrade to 4.1
I also want to avoid creating a new cluster with 3.6 version cause then I will have to shutdown all VMs again.
you don’t have to again if you keep 3.6 cluster in 4.1 setup. Thanks, michal
Thanks
G ps. The steps I had in mind were: upgrade serially hosts to Centos 7 migrate VMs there backup-restore engine to new Centos 7 machine _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

On 25/10/17 09:46, Michal Skrivanek wrote:
while you are still in 3.6 engine you need to upgrade that Default cluster to 3.6. This requires VMs power cycle to fully update everything. only then upgrade to 4.1
I also want to avoid creating a new cluster with 3.6 version cause then I will have to shutdown all VMs again.
you don’t have to again if you keep 3.6 cluster in 4.1 setup.
Thanks, michal
I've already updated my nodes to latest vdsm and Centos 7 by using an intermediate new cluster. I've live migrated the VMs to the new cluster. Didn't expect that to be available :) However I couldn't update my old cluster to 3.6 even with no VM running. It complained that the nodes could make it up to 3.5 only. Anyway that's old and now I'm in process of migrating the engine to a new el7 host. thanks G
participants (2)
-
Kapetanakis Giannis
-
Michal Skrivanek