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

Bug 1659650

Summary: Periodically check existing data centers and raise alert that 3.6/4.0 data center levels are not supported in RHV 4.3
Product: Red Hat Enterprise Virtualization Manager Reporter: Martin Perina <mperina>
Component: ovirt-engineAssignee: Jan Zmeskal <jzmeskal>
Status: CLOSED ERRATA QA Contact: Jan Zmeskal <jzmeskal>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.2.7CC: lsvaty, mgoldboi, ratamir, Rhev-m-bugs, sborella
Target Milestone: ovirt-4.2.8Keywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.2.8.2 Doc Type: Release Note
Doc Text:
Red Hat Virtualization 4.3 no longer supports the 3.6 and 4.0 data centers and cluster levels. This fix adds a service that runs weekly to evaluate existing data centers and raises an alert to audit the inability to upgrade to 4.3 if the data center is compatible with either versions 3.6, 4.0, or both versions.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-22 12:44:51 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:
Attachments:
Description Flags
Verification screenshot none

Description Martin Perina 2018-12-14 22:01:52 UTC 
Support for 3.6/4.0 hosts, clusters and data centers is going to be removed in oVirt/RHV 4.3 (see BZ1655115), so add a periodic service, which whould go over existing data centers and if 3.6/4.0 data center is found, raise an alert to audit log that those versions are not supported in RHV 4.3 and upgrade to RHV 4.3 is not possible without upgrading those data centers to newer versions.
Comment 1 Jan Zmeskal 2019-01-14 15:29:03 UTC 
Created attachment 1520559 [details]
Verification screenshot

Verified on 4.2.8.2.

I created (and initialized) DC and cluster with compatibility version 4.0. Then I restarted the engine. After that, expected alert could be seen.
Comment 3 errata-xmlrpc 2019-01-22 12:44:51 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, 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/RHBA-2019:0121