VM stuck in paused mode with Cluster Compatibility Version 3.6 on 4.2 cluster

Hi, we upgraded ovirt from version 4.1 to 4.2.6. Rebooted all vms. We missed two vms that were at Cluster Compatibility Version 3.6. There was a gluster/network IO problem and vms got paused. We were able to recover all the other vms from the paused state but we have two vms that won't run because: "Cannot run VM. The Custom Compatibility Version of VM VM_NAME (3.6) is not supported in Data Center compatibility version 4.1." Can we force the CCV of the paused vm to 4.1? Regards, -- Marco Crociani

I had something similar happen while upgrading. Didn’t find a way to fix the configs on the fly, but was able to un-pause the VMs using virsh, then proceed to handle the ovirt portions. Probably work for you as well.
From: Marco Lorenzo Crociani <marcoc@prismatelecomtesting.com> Subject: [ovirt-users] VM stuck in paused mode with Cluster Compatibility Version 3.6 on 4.2 cluster Date: September 20, 2018 at 11:10:48 AM CDT To: users
Hi, we upgraded ovirt from version 4.1 to 4.2.6. Rebooted all vms. We missed two vms that were at Cluster Compatibility Version 3.6. There was a gluster/network IO problem and vms got paused. We were able to recover all the other vms from the paused state but we have two vms that won't run because:
"Cannot run VM. The Custom Compatibility Version of VM VM_NAME (3.6) is not supported in Data Center compatibility version 4.1."
Can we force the CCV of the paused vm to 4.1?
Regards,
-- Marco Crociani _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/5XH3H6ADEY3WFY...

Hi, Darrell thanks, it worked. Regards, Marco On 20/09/2018 18:47, Darrell Budic wrote:
I had something similar happen while upgrading. Didn’t find a way to fix the configs on the fly, but was able to un-pause the VMs using virsh, then proceed to handle the ovirt portions. Probably work for you as well.
------------------------------------------------------------------------ *From:* Marco Lorenzo Crociani <marcoc@prismatelecomtesting.com <mailto:marcoc@prismatelecomtesting.com>> *Subject:* [ovirt-users] VM stuck in paused mode with Cluster Compatibility Version 3.6 on 4.2 cluster *Date:* September 20, 2018 at 11:10:48 AM CDT *To:* users
Hi, we upgraded ovirt from version 4.1 to 4.2.6. Rebooted all vms. We missed two vms that were at Cluster Compatibility Version 3.6. There was a gluster/network IO problem and vms got paused. We were able to recover all the other vms from the paused state but we have two vms that won't run because:
"Cannot run VM. The Custom Compatibility Version of VM VM_NAME (3.6) is not supported in Data Center compatibility version 4.1."
Can we force the CCV of the paused vm to 4.1?
Regards,
-- Marco Crociani _______________________________________________ Users mailing list -- users@ovirt.org <mailto:users@ovirt.org> To unsubscribe send an email to users-leave@ovirt.org <mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/5XH3H6ADEY3WFY...
participants (2)
-
Darrell Budic
-
Marco Lorenzo Crociani