Bug 1940672

Summary:	After upgrading RHVH 4.4.2 to 4.4.3 moves to non-operational due to missing CPU features : model_Cascadelake-Server
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Arik <ahadas>
Component:	Documentation	Assignee:	Eli Marcus <emarcus>
Status:	CLOSED CURRENTRELEASE	QA Contact:	rhev-docs <rhev-docs>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.4.3	CC:	abpatil, ahadas, aspauldi, ctomasko, dfodor, emarcus, jortialc, ljelinko, lsurette, mavital, mhicks, michal.skrivanek, pvilayat, qiyuan, sigbjorn.lie, srevivo
Target Milestone:	ovirt-4.4.5	Keywords:	Documentation, Reopened
Target Release:	4.4.5
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Previously, when Red Hat Virtualization Manager 4.4.3+ upgraded a host in a cluster that is set with Skylake/Cascadelake CPU type and compatibility level 4.4 (or lower), the host could become non-operational. In this release, the Red Hat Virtualization Manager blocks the upgrade of a host when the cluster is set with a secured Skylake/Cascadelake CPU type 1 (Secure Intel Skylake Client Family, Secure Intel Skylake Server Family, or Secure Intel Cascadelake Server Family) where the upgrade is likely to make the host non-operational. If the cluster is set with an insecure Skylake/Cascadelake CPU type 2 (Intel Skylake Client Family, Intel Skylake Server Family, or Intel Cascadelake Server Family) the user is notified with a recommendation to change the cluster to a secure Skylake/Cascadelake CPU type, but is allowed to proceed with the host upgrade. In order to make the upgraded host operational, the user must enable TSX at the operating system level.	Story Points:	---
Clone Of:	1905158	Environment:
Last Closed:	2021-04-18 15:52:04 UTC	Type:	---
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:	1905158
Bug Blocks:

Comment 1 Audrey Spaulding 2021-03-18 20:19:37 UTC

@ahadas, thanks for creating this doc bug for us. I'm going to move the text out of the Doc Text field, since you are proposing that we had it as a bug fix/doc update rather than a release note, if I understand correctly?

Comment 2 Arik 2021-03-18 21:23:21 UTC

I don't think that I know the alternatives - having a bug in the a section like "5.1.1. Bug Fix" in the release notes of "5.1. Red Hat Virtualization 4.4 General Availability (ovirt-4.4.1)" is fine

Comment 3 Audrey Spaulding 2021-03-19 12:37:51 UTC

Changed Doc Type from Bug Fix to Release Note.

Comment 4 Eli Marcus 2021-03-24 09:53:15 UTC

Hi Arik
please review this doc text: 

Previously, when Red Hat Virtualization Manager 4.4.3+ upgraded a host in a cluster that is set with Skylake/Cascadelake CPU type and compatibility level 4.4 (or lower), the host could become non-operational.
In this release, the Red Hat Virtualization Manager blocks the upgrade of a host when the cluster is set with a secured Skylake/Cascadelake CPU type 1 (Secure Intel Skylake Client Family, Secure Intel Skylake Server Family, or Secure Intel Cascadelake Server Family) where the upgrade is likely to make the host non-operational. 
If the cluster is set with an insecure Skylake/Cascadelake CPU type 2 (Intel Skylake Client Family, Intel Skylake Server Family, or Intel Cascadelake Server Family) the user is notified with a recommendation to change the cluster to a secure Skylake/Cascadelake CPU type, but is allowed to proceed with the host upgrade. In order to make the upgraded host operational, the user must enable TSX at the operating system level.

Comment 5 Arik 2021-03-24 09:57:24 UTC

Looks good to me, thanks