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

Bug 1623259

Summary:	Mark clusters with deprecated CPU type
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Marina Kalinin <mkalinin>
Component:	ovirt-engine	Assignee:	Steven Rosenberg <srosenbe>
Status:	CLOSED ERRATA	QA Contact:	Liran Rotenberg <lrotenbe>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.2.5	CC:	apinnick, lsurette, lveyde, mavital, michal.skrivanek, mtessun, rbarry, Rhev-m-bugs, srevivo, tburke
Target Milestone:	ovirt-4.2.7	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.2.7.3	Doc Type:	Enhancement
Doc Text:	In the current release, for compatibility versions 4.2 and 4.3, a warning in the Cluster screen indicates that the CPU types currently used are not supported in 4.3. The warning enables the user to change the cluster CPU type to a supported CPU type.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-11-05 15:02:41 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:
Bug Depends On:
Bug Blocks:	1540921, 1649817

Description Marina Kalinin 2018-08-28 20:41:48 UTC

If we are going to remove Conroe and Penryn CPUs from RHV 4.3, we should add a warning sign to the cluster with those CPUs in use now, RHV 4.2.z.

This will give the admins using those machines now the heads up and opportunity to plan ahead and purchase the needed hardware by the time RHV 4.3 is available.

Warning language should be something between the lines:
Information: This CPU type(Conroe/Penryn) is not going to be supported in the next minor version of RHV. 


In addition, we need to make sure that engine-setup is aware of this and would not upgrade, if the setup contains those CPU types. IF needed - please open a separate bug.

Comment 1 Marina Kalinin 2018-08-28 21:06:50 UTC

See also docs bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1623266

Comment 2 Michal Skrivanek 2018-08-29 07:56:25 UTC

we should be able to easily use ClusterAdditionalStatusColumn to display that similar to warning about old cluster level.
Same for all IBRS types we should show that they are not secure
Maybe two simple vdc_options to list all the CPUs we want to warn about because they are 1) insecure 2) deprecated and removed in next version

Comment 3 Ryan Barry 2018-09-07 20:43:17 UTC

AMD has not released security fixes for anything prior to Opteron_G4 (see https://www.amd.com/en/corporate/security-updates), so we should also mark Opteron_G[123] as deprecated.

Comment 4 Liran Rotenberg 2018-10-09 12:06:46 UTC

Verified on:
ovirt-engine-4.2.7.3-0.0.master.20181008113103.git4718e0f.el7.noarch

Steps:
1. Create a 4.2 cluster.
2. Set a CPU Type.
3. In clusters tab check for a warning.

Result:
Tested on Intel Conroe/Penryn, AMD G1/G2/G3.
On each i had the warning:
The CPU type (Intel Conroe/Penryn Family / AMD Opteron G1/G2/G3) will not be supported in the next minor version update.

Other CPU types have no warning as expected.

The engine-setup awareness will be taken care in bug: 1540921.

Comment 5 RHV bug bot 2018-10-18 11:39:26 UTC

WARN: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[Found non-acked flags: '{'rhevm-4.2.z': '?'}', ]

For more info please contact: rhv-devops: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[Found non-acked flags: '{'rhevm-4.2.z': '?'}', ]

For more info please contact: rhv-devops

Comment 6 Raz Tamir 2018-10-22 08:30:13 UTC

QE verification bot: the bug was verified upstream

Comment 8 errata-xmlrpc 2018-11-05 15:02:41 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-2018:3480