version: rhv- 4.4.4.7-0.1 ocp -4.7.0-0.nightly-2021-01-31-023653 steps: 1) Install a cluster with the VMs on High performance for master and worker node 2) verify that special configuration implements on rhv UI for worker and master node special configuration: CPU host passthrough - Disable ballooning - Enable serial console - Make the VM headless actual: when installing vms with High Performance, special configuration implement only for master node expected: when installing vms with High Performance, the special configuration should implement for master node and worker node
due to capacity constraints, we will be revisiting this bug in the upcoming sprint
@gzaidman what's the status on this please?
(In reply to Janos Pasztor from comment #3) > @gzaidman what's the status on this please? Wanted to handle it in the refactoring and add it to the go-ovirt-client
Waiting on changes in go-ovirt client, to be reviewed next week
Steps: 1) Change configuration before OCP installation, so that the worker VMs are high-performance. (vmType: high_performance) 2) Check that worker nodes have these options set as followed: Memory Ballooning - disabled Soundcard - disabled Headless mode - enabled VirtIO Serial Console - enabled Migration - only manual Pass-Through Host CPU - enabled Results: Worker nodes are created as high-performance with all the options set correctly. Verified in: ocp-4.12.0-0.nightly-2022-09-28-204419 rhvm-4.5.3-0.2.el8ev.noarch
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.12.0 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-2022:7399