Bug 2086936

Summary:	vsphere ipi should use cores by default instead of sockets
Product:	OpenShift Container Platform	Reporter:	Joseph Callen <jcallen>
Component:	Installer	Assignee:	Nobody <nobody>
Installer sub component:	openshift-installer	QA Contact:	jima
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	unspecified
Version:	4.11
Target Milestone:	---
Target Release:	4.11.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:	2022-08-10 11:12:25 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 Joseph Callen 2022-05-16 20:10:59 UTC

Platform: vsphere
Please specify: IPI
What happened?
https://github.com/openshift/installer/pull/5841

What did you expect to happen?

Set the NumCoresPerSocket to the same of NumCPUs.

Comment 3 jima 2022-05-19 09:13:00 UTC

Verified on 4.11.0-0.nightly-2022-05-18-171831 and passed, move bug to VERIFIED.

Use default platform configuration and install ipi cluster on vsphere successfully with expected config.

$ oc get clusterversion
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.11.0-0.nightly-2022-05-18-171831   True        False         21m     Cluster version is 4.11.0-0.nightly-2022-05-18-171831
worker:
$ govc vm.info -json jima17bug-mkc4v-worker-bqv5c | jq -r ".VirtualMachines[].Config.Hardware.NumCPU"
4
$ govc vm.info -json jima17bug-mkc4v-worker-bqv5c | jq -r ".VirtualMachines[].Config.Hardware.NumCoresPerSocket"
4

master:
$ govc vm.info -json jima17bug-mkc4v-master-0 | jq -r ".VirtualMachines[].Config.Hardware.NumCPU"
4
$ govc vm.info -json jima17bug-mkc4v-master-0 | jq -r ".VirtualMachines[].Config.Hardware.NumCoresPerSocket"
4

Comment 6 errata-xmlrpc 2022-08-10 11:12:25 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 (Important: OpenShift Container Platform 4.11.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:5069