Bug 1877675

Summary: [RFE] Introduce Datacenter and cluster level 4.5
Product: [oVirt] ovirt-engine Reporter: Martin Perina <mperina>
Component: GeneralAssignee: Eli Mesika <emesika>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Matyáš <pmatyas>
Severity: high Docs Contact:
Priority: high    
Version: 4.4.0CC: ahadas, bpelled, bugs, emesika, gveitmic, khakimi, ljelinko, lsvaty, michal.skrivanek, mkalinin, pelauter, usurse
Target Milestone: ovirt-4.4.3Keywords: FutureFeature
Target Release: ---Flags: mperina: ovirt-4.4?
mperina: planning_ack?
mperina: devel_ack+
lleistne: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.4.3.2, vdsm-4.4.30 Doc Type: Release Note
Doc Text:
We are going to introduce datacenter and cluster level 4.5, which will be available only on CentOS/RHEL 8.3 hypervisors with Advanced Virtualization 8.3 packages.
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-11 06:41:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1859494    
Bug Blocks: 1725166, 1745024, 1814565, 1836661, 1852718, 1853194, 1876605, 1878467, 1879074, 1879280    

Description Martin Perina 2020-09-10 07:35:09 UTC
We are going to introduce datacenter and cluster level 4.5, which will be available only on CentOS/RHEL 8.3 hypervisors with Advanced Virtualization 8.3 packages.

Comment 3 Petr Matyáš 2020-09-30 11:52:22 UTC
Verified on ovirt-engine-4.4.3.3-0.19.el8ev.noarch

Comment 4 Sandro Bonazzola 2020-11-11 06:41:52 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.

Comment 21 Lucia Jelinkova 2021-04-20 09:51:47 UTC
Yes, we should be careful when removing CPUs (hopefully that won't happen again). The same issue can occur also when the CPU definition changes, as it happened with noTXS recently. We introduced simple "translator" in the UI to handle it.

https://gerrit.ovirt.org/#/c/ovirt-engine/+/113616/