Bug 1950343 - [RFE] Set compatibility level 4.6 for Default DataCenter/Cluster during new installations of oVirt 4.4.7
Summary: [RFE] Set compatibility level 4.6 for Default DataCenter/Cluster during new i...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: General
Version: 4.4.6
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.4.7
: ---
Assignee: Martin Perina
QA Contact: Guilherme Santos
URL:
Whiteboard:
Depends On: 1950348
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-16 13:07 UTC by Martin Perina
Modified: 2021-07-06 07:28 UTC (History)
3 users (show)

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
Clone Of:
: 1950348 (view as bug list)
Environment:
Last Closed: 2021-07-06 07:28:10 UTC
oVirt Team: Infra
Embargoed:
pm-rhel: ovirt-4.4+
pelauter: planning_ack+
mperina: devel_ack+
gdeolive: testing_ack+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 114324 0 master MERGED core: Set 4.6 compatibility level to Default DC/CL 2021-06-08 14:42:43 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.