Normal Description of problem:
openshift install fails with "failed to lease wait: Invalid configuration for device '0'. generated yaml below: additionalTrustBundlePolicy: Proxyonly apiVersion: v1 baseDomain: XXX compute: - architecture: amd64 hyperthreading: Enabled name: worker platform: vsphere: coresPerSocket: 2 cpus: 8 memoryMB: 40960 osDisk: diskSizeGB: 150 zones: - generated-failure-domain replicas: 3 controlPlane: architecture: amd64 hyperthreading: Enabled name: master platform: vsphere: coresPerSocket: 2 cpus: 4 memoryMB: 32768 osDisk: diskSizeGB: 150 zones: - generated-failure-domain replicas: 3 metadata: creationTimestamp: null name: dc3 networking: clusterNetwork: - cidr: 10.128.0.0/14 hostPrefix: 23 machineNetwork: - cidr: 10.0.0.0/16 networkType: OVNKubernetes serviceNetwork: - 172.30.0.0/16 platform: vsphere: apiVIP: 172.21.0.20 apiVIPs: - 172.21.0.20 cluster: SA-LAB datacenter: OVH-SA defaultDatastore: DatastoreOCP failureDomains: - name: generated-failure-domain region: generated-region server: XXX topology: computeCluster: /OVH-SA/host/SA-LAB datacenter: OVH-SA datastore: /OVH-SA/datastore/DatastoreOCP networks: - ocpdemo resourcePool: /OVH-SA/host/SA-LAB/Resources zone: generated-zone ingressVIP: 172.21.0.21 ingressVIPs: - 172.21.0.21 network: ocpdemo ~~~ Truncated~~~
Version-Release number of selected component (if applicable):
How reproducible:
always
Steps to Reproduce:
1.openshift-install create cluster
2.choose Vsphere
3.
Actual results:
Error
Expected results:
Cluster creation
Additional info:
- links to
-
RHEA-2024:6122
OpenShift Container Platform 4.18.z bug fix update
[OCPBUGS-37628] vsphere platform spec validation failure when both legacy and current fields are used
Reviewed the conversion code. There is no way that mixing and matching would cause an issue but it still isn't recommended. Added warning messages as the fix to this issue.
Since the problem described in this issue should be resolved in a recent advisory, it has been closed.
For information on the advisory (Important: OpenShift Container Platform 4.18.1 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-2024:6122