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

Bug 1877668

Summary:	model_Cascadelake-Server-noTSX (cpu flag) is missing from vdc_options table
Product:	[oVirt] ovirt-engine	Reporter:	Beni Pelled <bpelled>
Component:	General	Assignee:	Lucia Jelinkova <ljelinko>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Beni Pelled <bpelled>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.4.3.1	CC:	ahadas, bugs, dfodor, hhaberma, mavital, michal.skrivanek
Target Milestone:	ovirt-4.4.3	Keywords:	Reopened
Target Release:	---	Flags:	pm-rhel: ovirt-4.4+ mavital: testing_plan_complete-
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.4.3.8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-11 06:42:16 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 Beni Pelled 2020-09-10 06:59:39 UTC

Description of problem:
The ServerCPUList column on vdc_options table is missing model_Cascadelake-Server-noTSX which causes cascadelake hosts (that reported model_Cascadelake-Server-noTSX as cpu type) to be added with different CPU type during HE installation. 

Version-Release number of selected component (if applicable):
ovirt-engine-4.4.3.1-0.7.el8ev.noarch
libvirt-6.6.0-4.module+el8.3.0+7883+3d717aa8.x86_64
vdsm-4.40.28-1.el8ev.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Run HE setup on a host with Cascadelake CPU.


Actual results:
The host will be added with `Secure Intel Broadwell Family` as CPU Type

Expected results:
The host should be added with `Intel Cascadelake Server Family` as CPU Type

Comment 3 Beni Pelled 2020-10-25 14:05:31 UTC

Verified with:
- ovirt-engine-4.4.3.8-0.1.el8ev.noarch
- libvirt-6.6.0-6.module+el8.3.0+8125+aefcf088.x86_64
- vdsm-4.40.35-1.el8ev.x86_64

Verification steps:
1. Run HE setup on a host with Cascadelake CPU.

Result:
- The setup completed successfully and the host 'Secure Intel Cascadelake Server Family' as cpu-type.

Comment 4 Sandro Bonazzola 2020-11-11 06:42:16 UTC

This bugzilla is included in oVirt 4.4.3 release, published on November 10th 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.3 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.