Bug 1965921 - [oVirt] High performance VMs shouldn't be created with Existing policy
Summary: [oVirt] High performance VMs shouldn't be created with Existing policy
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.8
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.8.0
Assignee: Gal Zaidman
QA Contact: Michael Burman
Depends On:
TreeView+ depends on / blocked
Reported: 2021-05-31 07:04 UTC by Gal Zaidman
Modified: 2021-07-27 23:10 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-07-27 23:10:35 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift installer pull 4969 0 None open Bug 1965921: [oVirt] High performance VMs shouldn't be created with Existing policy 2021-05-31 07:59:18 UTC
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 23:10:48 UTC

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-

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.


Note You need to log in before you can comment on or make changes to this bug.