Bug 1848922

Summary: Setting vm to high-performance doesn't automatically set high-performance features
Product: OpenShift Container Platform Reporter: Guilherme Santos <gdeolive>
Component: InstallerAssignee: Liran Rotenberg <lrotenbe>
Installer sub component: OpenShift on RHV QA Contact: Lucie Leistnerova <lleistne>
Status: CLOSED DUPLICATE Docs Contact:
Severity: high    
Priority: medium CC: dougsland, gzaidman, hpopal, lrotenbe, sigbjorn.lie
Version: 4.4   
Target Milestone: ---   
Target Release: 4.7.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-01-21 08:56:17 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 Guilherme Santos 2020-06-19 09:31:30 UTC
Description of problem:
When installing ocp using IPI through the configuration file, it's possible to set the vm_type to high performance. However, no high performance configurations are set doing it so (cpu pinning, numa, huge pages...), only the icon changes. 
This happen because the high performance type doesn't automatically set those things in rhv anyway, when choosing high-perfomance in the UI a message guiding the user to manually set the high performance settings show up:


The following recommended settings for running the High Performance type with the optimal configuration were not detected. Please consider manually changing of the following before applying:
CPU PINNING: 
Please pin virtual CPUs to specific host(s) physical CPUs. This should be done by: 
1. selecting the "Start running on: Specific Host(s)" option 
2. Setting the "CPU Pinning topology" field and verifying that the configuration fits pinned host(s)'s configuration: 
guest number of virtual sockets <= host's number of sockets. 
guest number of cores per virtual socket <= host's number of cores per socket. 
guest number of threads per core <= host's number of threads per core.
VIRTUAL NUMA AND NUMA PINNING: 
1. Please configure virtual NUMA nodes. Note that it requires a NUMA-enabled pinned host(s). 
2. Then please pin those virtual NUMA nodes to physical NUMA nodes on the pinned host(s). 
3. Verify that virtual NUMA topology fits the host's physical NUMA topology.
HUGE PAGES: 
1. Please set huge pages configuration via the "Custom Properties" tab (huge page size is required in KB). 
2. For setting the huge page size, verify that the virtual huge pages setting fits the pinned physical host(s) setting: 
virtual huge pages size equals to the huge pages size on the pinned host(s). 
virtual memory size fits into free huge pages of the given size on the pinned host(s). 
3. Consider setting huge pages size to the biggest size that is still supported by the pinned host(s).


Version-Release number of the following components:
openshift-install-linux-4.4.0-0.nightly-2020-06-15-203705

How reproducible:
always

Steps to Reproduce:
1. Deploy ocp setting vm_type for the nodes as high-performance
2.
3.

Actual results:
No high-performance settings automatically set

Comment 1 Douglas Schilling Landgraf 2020-07-09 12:22:21 UTC
due to capacity constraints we will be revisiting this bug in the upcoming sprint

Comment 2 Sandro Bonazzola 2020-09-14 09:49:56 UTC
same as comment #1

Comment 3 Sandro Bonazzola 2020-10-22 11:33:53 UTC
due to capacity constraints we will be revisiting this bug in the upcoming sprint

Comment 4 Sandro Bonazzola 2020-12-03 12:47:05 UTC
Needs to extend API on oVirt side to allow this to happen.

Comment 6 Gal Zaidman 2021-01-21 08:56:17 UTC
This bug was for the terraform provider, we had a different bug for the installer.
The work on the tf-provider is done, marking this as a duplicate of the installer bug.
THANKS LIRAN!

*** This bug has been marked as a duplicate of bug 1912828 ***