-
Bug
-
Resolution: Done-Errata
-
Major
-
4.16.0, 4.18.z
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
No
-
None
-
None
-
Installer Sprint 266, Installer Sprint 267, Installer Sprint 268, Installer Sprint 269
-
4
-
Done
-
Bug Fix
-
-
None
-
None
-
None
-
None
Description of problem:
IPI deployment of OCP on vsphere fails to complete.
Network operator in degraded state:
spec: {}
status:
conditions:
- lastTransitionTime: "2024-07-04T10:30:43Z"
message: 'Error while synchronizing spec and status of infrastructures.config.openshift.io/cluster:
Error on validating API VIPs and Machine Networks: VIP ''10.xx.xx.xx'' cannot
be found in any machine network'
oc get infrastructure shows the following:
spec:
cloudConfig:
key: config
name: cloud-provider-config
platformSpec:
type: VSphere
vsphere:
apiServerInternalIPs:
- 10.xx.xx.xx
failureDomains:
- name: generated-failure-domain
region: generated-region
server: vcenter.url.com
topology:
computeCluster: /OpenShift-DC/host/OCP
datacenter: OpenShift-DC
datastore: /OpenShift-DC/datastore/OCP-PNQ-Datastore
networks:
- network-id
resourcePool: /OpenShift-DC/host/OCP/Resources
template: /OpenShift-DC/vm/ocp4ipi07-txnr6-rhcos-generated-region-generated-zone
zone: generated-zone
ingressIPs:
- 10.xx.xx.xx
machineNetworks:
- 10.0.0.0/16
The machine network is added as default value `10.0.0.0/16` which was not provided when running create cluster command.
Version-Release number of selected component (if applicable):
How reproducible:
100 %
Steps to Reproduce:
1. openshift-installer create cluster
2. post installation check network operator status
3. oc get infrastructure -o yaml
Actual results:
Network operator in degraded state
Expected results:
All operator should be available.
Additional info:
- links to
-
RHEA-2024:11038
OpenShift Container Platform 4.19.z bug fix update