Bug 2096287 - Can not set default cluster CPU level
Summary: Can not set default cluster CPU level
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Installation
Version: 4.10.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 4.10.3
Assignee: Simone Tiraboschi
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On: 2103206
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-13 12:43 UTC by Fabian Deutsch
Modified: 2022-07-20 16:01 UTC (History)
5 users (show)

Fixed In Version: hco-bundle-registry-container-v4.10.3-9, hyperconverged-cluster-operator-container-v4.10.3-2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-07-20 16:01:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt hyperconverged-cluster-operator pull 2004 0 None Merged Expose a knob to let the user tune default CPU model 2022-06-14 21:48:15 UTC
Github kubevirt hyperconverged-cluster-operator pull 2005 0 None Merged [release-1.7] Expose a knob to let the user tune default CPU model 2022-06-15 07:07:57 UTC
Github kubevirt hyperconverged-cluster-operator pull 2006 0 None Merged [release-1.6] Expose a knob to let the user tune default CPU model (#… 2022-06-15 07:07:59 UTC
Github kubevirt hyperconverged-cluster-operator pull 2024 0 None Merged [release-1.6] Fix a typo in DefaultCPUModel HCO API field 2022-07-03 07:59:38 UTC
Red Hat Product Errata RHEA-2022:5675 0 None None None 2022-07-20 16:01:47 UTC

Description Fabian Deutsch 2022-06-13 12:43:24 UTC 
Description of problem:
As a cluster admin I am not able to set the default cluster model via the HCO CR.

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

How reproducible:
Always

Steps to Reproduce:
1. Try to set the defautl CPU model of the cluster to i.e. IceLake when installing HCO
2.
3.

Actual results:
No field to set the default cpu model

Expected results:
A field to set the default CPU model to be then used by KubeVirt

Additional info:
HCO should have a field to allow a cluster admin to set the default CPU model, this CPU model should then be used by HCO to set the field in the KubeVirt CR (KubeVirt.configuration.cpuModel). If not provided then HCO should not set anything in the KubeVirt CR
Comment 2 SATHEESARAN 2022-07-01 16:20:29 UTC 
The implementation of cluster vide default-CPU-Model has a problem.
There is a typo with the keyword.

Instead of using 'defaultCPUModel', the patch used 'defaulCPUMode' ( note that the 't' is missed in defaul't' )


When editing HCO CR, this value needs to be added to .spec section as 'defaulCPUModel' which is inconsistent.

Because of this reason, marking this bug as FAILED by moving this bug to ASSIGNED
Comment 4 SATHEESARAN 2022-07-06 12:11:48 UTC 
Verified with hco-bundle v4.10.3-12, and hyperconverged-cluster-operator-v4.10.3-2

'defaultCPUModel' is now available with HCO CR and when set with the proper CPU Model,
kubevirt and VMI is updated with the same CPU Model.

When removing the 'defaultCPUModel' from HCO CR, removes the same from kubevirt CR.
Newly created VM and restarting the existing VM, thereafter gets the CPU model as 'host-model'
as expected.

Based on this observation, marking this bug as VERIFIED
Comment 6 Fabian Deutsch 2022-07-12 09:04:17 UTC 
I've filed 2106266 to follow up with documentation for this new field.
Comment 11 errata-xmlrpc 2022-07-20 16:01:37 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 (OpenShift Virtualization 4.10.3 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/RHEA-2022:5675
Note You need to log in before you can comment on or make changes to this bug.