-
Bug
-
Resolution: Done-Errata
-
Minor
-
None
-
4.15, 4.16
-
None
-
Low
-
None
-
False
-
-
N/A
-
Release Note Not Required
-
Done
This is a clone of issue OCPBUGS-38551. The following is the description of the original issue:
—
Description of problem:
If multiple NICs are configured in install-config, the installer will provision nodes properly but will fail in bootstrap due to API validation. > 4.17 will support multiple NICs, < 4.17 will not and will fail. Aug 15 18:30:57 2.252.83.01.in-addr.arpa cluster-bootstrap[4889]: [#1672] failed to create some manifests: Aug 15 18:30:57 2.252.83.01.in-addr.arpa cluster-bootstrap[4889]: "cluster-infrastructure-02-config.yml": failed to create infrastructures.v1.config.openshift.io/cluster -n : Infrastructure.config.openshift.io "cluster" is invalid: [spec.platformSpec.vsphere.failureDomains[0].topology.networks: Too many: 2: must have at most 1 items, <nil>: Invalid value: "null": some validation rules were not checked because the object was invalid; correct the existing errors to complete validation]
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
- blocks
-
OCPBUGS-38687 vsphere: install-config allows configuration of multiple NICs
- ON_QA
- clones
-
OCPBUGS-38551 vsphere: install-config allows configuration of multiple NICs
- Verified
- is blocked by
-
OCPBUGS-38551 vsphere: install-config allows configuration of multiple NICs
- Verified
- is cloned by
-
OCPBUGS-38687 vsphere: install-config allows configuration of multiple NICs
- ON_QA
- links to
-
RHEA-2024:3718 OpenShift Container Platform 4.17.z bug fix update