Bug 1890430

Summary:	Kubevirt / OpenShift Virtualization provider - the cluster/host cpu mismatch message
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Artur Socha <asocha>
Component:	ovirt-engine	Assignee:	Arik <ahadas>
Status:	CLOSED NEXTRELEASE	QA Contact:	Lucie Leistnerova <lleistne>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	4.4.2	CC:	ahadas, emarcus, ljelinko, michal.skrivanek, mperina
Target Milestone:	ovirt-4.4.4
Target Release:	4.4.4
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.4.4, vdsm-jsonrpc-java-1.5.7	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-13 16:32:01 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 Artur Socha 2020-10-22 07:55:23 UTC

Description of problem:
Hosts managed by OpenShift (OCP) and imported into RHVM by 'Kubernetes/OpenShift Virtualization' provider may have different CPU types. The cluster created in RHVM as part the integration has only one CPU type allowed.
There is an validation message about the CPU type mismatch that should be removed for such cluster(Kubernetes/OpenShift Virtualization integration) because such requirement is not valid for OCP managed environment.

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


Expected results:
No 'Cluster has hosts with CPUs not matching the clusters CPU Type. VMa are running in a degraded mode' message on hosts list.

Comment 1 Michal Skrivanek 2020-10-23 07:29:23 UTC

please always fill in severity and ideally also target milestone

Comment 2 Artur Socha 2020-10-23 08:10:06 UTC

I've set serverity to low because this issue can only mislead user but is not causing any harm. Happy to increase it if necessary. 
We will discuss/set the target milestone on Monday on our infra grooming. Putting 4.4.4 as a placeholder.

Comment 5 Casper (RHV QE bot) 2020-11-13 16:32:01 UTC

This bug has a low overall severity and passed automated regreession suite, it is not going to be further verified by QE. If you believe a special care is required feel free to re-open to ON_QA status