Bug 1847513 - [UPGRADE] failed to change the cluster compatibility version from 4.3 > 4.4 while VMs running on the cluster.
Summary: [UPGRADE] failed to change the cluster compatibility version from 4.3 > 4.4 w...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.4.1.2
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ovirt-4.4.1
: 4.4.1.5
Assignee: Liran Rotenberg
QA Contact: Nikolai Sednev
URL:
Whiteboard:
: 1856791 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-16 14:21 UTC by Kobi Hakimi
Modified: 2020-08-17 10:25 UTC (History)
8 users (show)

Fixed In Version: ovirt-engine-4.4.1.5
Doc Type: Bug Fix
Doc Text:
When you change the cluster compatibility version, it can also update the compatibility version of the virtual machines. If the update fails, it rolls back the changes. Previously, chipsets and emulated machines were not part of the cluster update. The current release fixes this issue. Now, you can also update chipsets and emulator machines when you update the cluster compatibility version.
Clone Of:
Environment:
Last Closed: 2020-07-08 08:26:53 UTC
oVirt Team: Virt
Embargoed:
pm-rhel: ovirt-4.4+
aoconnor: blocker+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 109735 0 master MERGED core: fix UpdateVmCommand for UpdateClusterCommand 2020-12-01 08:53:02 UTC

Description Kobi Hakimi 2020-06-16 14:21:08 UTC
Description of problem:
[UPGRADE] failed to change the cluster compatibility version from 4.3 > 4.4 while VMs running on the cluster.

Version-Release number of selected component (if applicable):
ovirt-engine-4.3.10.3-0.2.el7.noarch
ovirt-engine-4.4.1.2-0.10.el8ev.noarch

How reproducible:
100%

Steps to Reproduce:
Upgrade from 4.3 to 4.4(this case is related to hosted engine environment):
1. Backup the engine in 4.3 to file.
2. Provision the first host.
3. Deploy the hosted engine 4.4 by restore from the backup file.
4. Upgrade the hosts one by one. (by maintenance > remove from engine > provision to rhel-8.2 > Add them back to engine).
5. Update the compatibility version of the Clusters from 4.3 to 4.4

Actual results:
when the cluster has running VM's we got the following error:

"""
Error while executing action: Update of cluster compatibility version failed because there are VMs/Templates [golden_env_mixed_virtio_3_1, golden_env_mixed_virtio_3_0, golden_env_mixed_virtio_1_0, HostedEngine, golden_env_mixed_virtio_2_0, golden_env_mixed_virtio_2_1, golden_env_mixed_virtio_1_1] with incorrect configuration. To fix the issue, please go to each of them, edit, change the Custom Compatibility Version of the VM/Template to the cluster level you want to update the cluster to and press OK. If the save does not pass, fix the dialog validation. After successful cluster update, you can revert your Custom Compatibility Version change.

"""

Expected results:
to be able to upgrade the cluster from previous version to the latest version without downtime of the VMs.

Additional info:

Comment 1 Michal Skrivanek 2020-06-17 04:04:06 UTC
logs?

Comment 3 Nikolai Sednev 2020-07-06 13:13:08 UTC
Works for me on latest Software Version:4.4.1.7-0.3.el8ev.
ovirt-hosted-engine-ha-2.4.4-1.el8ev.noarch
ovirt-hosted-engine-setup-2.4.5-1.el8ev.noarch
Linux 4.18.0-193.12.1.el8_2.x86_64 #1 SMP Thu Jul 2 15:48:14 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux release 8.2 (Ootpa)

Reported issue no longer exists.

Comment 4 Sandro Bonazzola 2020-07-08 08:26:53 UTC
This bugzilla is included in oVirt 4.4.1 release, published on July 8th 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.1 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.

Comment 5 Michal Skrivanek 2020-07-15 05:08:38 UTC
*** Bug 1856791 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.