Bug 1950343

Summary: [RFE] Set compatibility level 4.6 for Default DataCenter/Cluster during new installations of oVirt 4.4.7
Product: [oVirt] ovirt-engine Reporter: Martin Perina <mperina>
Component: GeneralAssignee: Martin Perina <mperina>
Status: CLOSED CURRENTRELEASE QA Contact: Guilherme Santos <gdeolive>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.4.6CC: bugs, gdeolive, pelauter
Target Milestone: ovirt-4.4.7Keywords: FutureFeature
Target Release: ---Flags: pm-rhel: ovirt-4.4+
pelauter: planning_ack+
mperina: devel_ack+
gdeolive: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.4.7.4 Doc Type: Release Note
Doc Text:
Default DataCenter/Cluster will be set to compatibility level 4.6 on new installations of oVirt 4.4.7
Story Points: ---
Clone Of:
: 1950348 (view as bug list) Environment:
Last Closed: 2021-07-06 07:28:10 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: 1950348    
Bug Blocks:    

Description Martin Perina 2021-04-16 13:07:49 UTC
DataCenter/Cluster compatibility level 4.6 has been introduced in oVirt 4.4.6 (BZ1933974), but it was not set as default compatibility level on new installations, because it requires CentOS 8.4 (or CentOS Stream 8) with Advanced Virtualization 8.4 (libvirt >= 7.0.0). So in oVirt 4.4.7 compatibility 4.6 will be set to Default DC/Cluster upon new installations

Comment 1 Guilherme Santos 2021-06-28 15:14:31 UTC
Verified on:
ovirt-engine-4.4.7.4-0.9.el8ev.noarch

Cluster with Compatibility level of 4.6 present by default in new RHV installation

Comment 2 Sandro Bonazzola 2021-07-06 07:28:10 UTC
This bugzilla is included in oVirt 4.4.7 release, published on July 6th 2021.

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