Bug 1940672 - After upgrading RHVH 4.4.2 to 4.4.3 moves to non-operational due to missing CPU features : model_Cascadelake-Server
Summary: After upgrading RHVH 4.4.2 to 4.4.3 moves to non-operational due to missing C...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation
Version: 4.4.3
Hardware: All
OS: Linux
high
high
Target Milestone: ovirt-4.4.5
: 4.4.5
Assignee: Eli Marcus
QA Contact: rhev-docs@redhat.com
URL:
Whiteboard:
Depends On: 1905158
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-18 20:04 UTC by Arik
Modified: 2021-04-18 15:52 UTC (History)
16 users (show)

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.
Clone Of: 1905158
Environment:
Last Closed: 2021-04-18 15:52:04 UTC
oVirt Team: Virt
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1905158 1 high CLOSED After upgrading RHVH 4.4.2 to 4.4.3 moves to non-operational due to missing CPU features : model_Cascadelake-Server 2024-10-01 17:10:39 UTC

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
Note You need to log in before you can comment on or make changes to this bug.