Bug 1965921

Summary:	[oVirt] High performance VMs shouldn't be created with Existing policy
Product:	OpenShift Container Platform	Reporter:	Gal Zaidman <gzaidman>
Component:	Installer	Assignee:	Gal Zaidman <gzaidman>
Installer sub component:	OpenShift on RHV	QA Contact:	Michael Burman <mburman>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	urgent
Priority:	urgent
Version:	4.8
Target Milestone:	---
Target Release:	4.8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-07-27 23:10:35 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Gal Zaidman 2021-05-31 07:04:11 UTC

Description of problem:

RHV changed the behavior of creating High-Performance VMs.
In the past when creating a High-Performance VM it would be created with Existing auto pining policy, but now Existing is removed and shouldn't be used.

We need to update the terraform provider that is used within the Openshift installer to consume the changes.

How to test:
1. Install an Openshift Cluster with High Performance Nodes.
2. Check on RHV that the VMs were created with no auto pining policy

Comment 3 Michael Burman 2021-06-03 06:18:40 UTC

Verified on - 4.8.0-0.nightly-2021-06-02-025513 with rhvm-4.4.6.8-0.1.el8ev.noarch

Comment 6 errata-xmlrpc 2021-07-27 23:10:35 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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), 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/RHSA-2021:2438