Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2035559

Summary:	RHV 4.4.9 - error setting Cluster Compatibility Version to 4.6
Product:	[oVirt] ovirt-engine	Reporter:	Donald Berry <dberry>
Component:	BLL.Virt	Assignee:	Shmuel Melamud <smelamud>
Status:	CLOSED CURRENTRELEASE	QA Contact:	meital avital <mavital>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.4.9	CC:	ahadas, bugs, jpasztor, lrotenbe, mdunnett, mtessun, mzamazal, smelamud, wlovaton
Target Milestone:	ovirt-4.5.3	Flags:	pm-rhel: ovirt-4.5?
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-08-18 11:52:29 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Donald Berry 2021-12-24 16:33:23 UTC

Description of problem:

After updating to RHV 4.4.9 (RHHI-V 1.8), got an alert:

"Data Center Default compatibility version is 4.5, which is lower than latest available version 4.6. Please upgrade your Data Center to latest version to successfully finish upgrade of your setup."

Tried to set Cluster Compatibility Version (change from 4.5 to 4.6):
Compute/Clusters/<cluster>/edit/general/compatibility version

Got an error:

"Error while executing action: Cannot update cluster because the update triggered update of the VMs/Templates and it failed for the following: (6 OCP coreOS VMs). To fix the issue, please go to each of them, edit, change the Custom Compatibility Version (or other fields changed previously in the cluster dialog) 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 (or other changes). If the problem still persists, you may refer to the engine.log file for further details."

None of the VMs have a custom compatibility level set. All say:
Operating System: Red Hat Enterprise Linux CoreOS
Cluster Compatibility Version: 4.5

Version-Release number of selected component (if applicable):

[root@rhvm2 ~]# rpm -q rhvm
rhvm-4.4.9.5-0.1.el8ev.noarch

[root@dell-r640-04 ~]# rpm -q redhat-release-virtualization-host
redhat-release-virtualization-host-4.4.9-3.el8ev.x86_64

Comment 3 Arik 2022-01-02 18:26:15 UTC

The error doesn't seem to cover that cluster-upgrade failure (I don't see CLUSTER_CANNOT_UPDATE_CLUSTER_FAILED_TO_UPDATE_VMS there)
Can you please double check it's the right log?

Comment 4 Arik 2022-01-03 12:40:08 UTC

(In reply to Arik from comment #3)
> The error doesn't seem to cover that cluster-upgrade failure (I don't see
> CLUSTER_CANNOT_UPDATE_CLUSTER_FAILED_TO_UPDATE_VMS there)
> Can you please double check it's the right log?

OK, the aforementioned errors appear in that log but not the failures of UpdateVm/UpdateVmTemplate

Comment 6 Lucia Jelinkova 2022-01-03 13:55:48 UTC

The error log contains some validation messages for update VM:

Validation of action 'UpdateVm' failed for user admin@internal-authz. Reasons: VAR__ACTION__UPDATE,VAR__TYPE__VM,ACTION_TYPE_FAILED_ILLEGAL_NUM_OF_MONITORS

Inspecting the details of the offended VMs showed that they are set with Video type: Bochs and Graphics protocol: None which is illegal configuration and is probably a bug. Opening edit dialog changes it automatically to QXL and SPICE, which is probably a different bug. 

To allow the cluster upgrade to pass, please update the offending VMs and their video/graphics configuration manually

To help us debug the issue, could you please provide some details about how the VMs were created / how they possibly could get to that illegal configuration?

Comment 19 Milan Zamazal 2022-07-18 12:58:53 UTC

Also, could it be possibly also related to BZ 2106349?

Comment 21 Milan Zamazal 2022-08-18 11:52:29 UTC

The problem is apparently not present anymore. Please reopen if it is still present in the current version.