The change is flagged as an enhancement so Doc Type set accordingly. https://github.com/openshift/installer/commit/ea437be225b14fd75a29c881c0ce1c2e9767b61f
before fix: set num_cpus: 6: output error: level=error msg=Error: error powering on virtual machine: powerOn task for vm "/SDDC-Datacenter/vm/wwei-bugtest-fb4kx/wwei-bugtest-fb4kx-master-0" failed: Module CPUID power on failed. after fix: set num_cpus: 6: coresPerSocket: output error: level=fatal msg=failed to fetch Master Machines: failed to load asset "Install Config": invalid "install-config.yaml" file: controlPlane.platform.vsphere.cpus: Invalid value: 6: numCPUs specified should be a multiple of cores per socket which is by default 4 set num_cpus: coresPerSocket: 6 ./openshift-install create manifests --dir ./ FATAL failed to fetch Master Machines: failed to load asset "Install Config": invalid "install-config.yaml" file: compute[0].platform.vsphere.coresPerSocket: Invalid value: 6: cores per socket must be less than number of CPUs which is by default 4 set num_cpus: 4 coresPerSocket: 6 ./openshift-install create manifests --dir ./ FATAL failed to fetch Master Machines: failed to load asset "Install Config": invalid "install-config.yaml" file: compute[0].platform.vsphere.coresPerSocket: Invalid value: 6: cores per socket must be less than number of CPUs set num_cpus: 6 coresPerSocket: 4 ./openshift-install create manifests --dir ./ FATAL failed to fetch Master Machines: failed to load asset "Install Config": invalid "install-config.yaml" file: compute[0].platform.vsphere.cpus: Invalid value: 6: numCPUs specified should be a multiple of cores per socket
Is this going to be backported to 4.10?
reproduce version: registry.ci.openshift.org/ocp/release:4.9.0-0.nightly-2022-03-03-053721 verified version: registry.ci.openshift.org/ocp/release:4.11.0-0.nightly-2022-03-04-063157 the details refer to comment 4 above
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