Bug 1954486

Summary:	Default cluster configuration for obsoleteCPUs and minCPU does not exist
Product:	Container Native Virtualization (CNV)	Reporter:	Ruth Netser <rnetser>
Component:	Installation	Assignee:	Nahshon Unna-Tsameret <nunnatsa>
Status:	CLOSED ERRATA	QA Contact:	ibesso <ibesso>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	4.8.0	CC:	cnv-qe-bugs, ibesso, kmajcher, nunnatsa, stirabos
Target Milestone:	---
Target Release:	4.8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	hco-bundle-registry-container-v4.8.0-305	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-07-27 14:31:30 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ruth Netser 2021-04-28 08:58:05 UTC

Description of problem:
Prior to 4.8.0, obsoleteCPUs and minCPU configuration was part of kubevirt-cpu-plugin-configmap.

In 4.8.0, the default configuration is missing (does not exist in hco/kv/ssp CRs and the configmap is not created).

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

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Nahshon Unna-Tsameret 2021-04-28 13:41:35 UTC

The default values are pre-defined in KubeVirt and are not visible. 

https://github.com/kubevirt/hyperconverged-cluster-operator/pull/1288 mitigates this by populating the default list of obsolete CPU models in KV, and only allow adding new ones, but not removing them.

Comment 2 ibesso 2021-05-27 19:31:09 UTC

Using a cluster deployed from scratch with 4.8.0:
IIB: registry-proxy.engineering.redhat.com/rh-osbs/iib:76375
HCO:[v4.8.0-350]

HCO CR does not have the obsoleteCPUs fields nor the minCPUModel scalar.
KubeVirt CR has the obsoleteCPUModels list, but the minCPUModel scalar is missing.


@nunnatsa ?

Comment 3 Nahshon Unna-Tsameret 2021-05-31 07:00:29 UTC

HCO does not need to have anything in the CR, unless the administrator wants to add more CPUs to the obsoleteCPUs list, or to change the default minCPUModel. KV also uses default default for the minCPUModel field, so if its empty both in KV and HCO, that's fine.

Please read the details here: https://github.com/kubevirt/hyperconverged-cluster-operator/blob/main/docs/cluster-configuration.md#cpu-plugin-configurations

Comment 4 ibesso 2021-05-31 08:18:45 UTC

Verified with a cluster installed with CNV 2.6.2 and upgraded to CNV 4.8.0
-----------------------------------------------------------------
IIB: registry-proxy.engineering.redhat.com/rh-osbs/iib:76375
HCO:[v4.8.0-350]

HCO CR does not have any of those fields.
By default KubeVirt CR has obsoleteCPUModels by default (spec.configuration.obsoleteCPUModels):
      "486": true
      Conroe: true
      athlon: true
      core2duo: true
      coreduo: true
      kvm32: true
      kvm64: true
      n270: true
      pentium: true
      pentium2: true
      pentium3: true
      pentiumpro: true
      phenom: true
      qemu32: true
      qemu64: true

Also, by default, KubeVirt CR does not have minCPUModel visibile.

Moving to VERIFIED.

Comment 7 errata-xmlrpc 2021-07-27 14:31:30 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Virtualization 4.8.0 Images), and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHSA-2021:2920