-
Bug
-
Resolution: Won't Do
-
Undefined
-
None
-
4.16.0
-
None
Description of problem:
Setup cluster using ELB which ip is not in machineNetworks, eg. 10.10.137.32 is the ELB ip and machineNetworks CIDR is 192.168.80.0/22. After cluster is ready. the network operator show error: "network 4.16.0-0.nightly-multi-2024-05-16-165918 True True True 51m Error while synchronizing spec and status of infrastructures.config.openshift.io/cluster: Error on validating API VIPs and Machine Networks: VIP '10.10.137.32' cannot be found in any machine network"
Version-Release number of selected component (if applicable):
4.16.0-0.nightly-multi-2024-05-16-165918
How reproducible:
always
Steps to Reproduce:
1. setup cluster with ELB which is not in machineNetworks and LB is usermanaged 2. 3.
Actual results:
the network operator show error: "network 4.16.0-0.nightly-multi-2024-05-16-165918 True True True 51m Error while synchronizing spec and status of infrastructures.config.openshift.io/cluster: Error on validating API VIPs and Machine Networks: VIP '10.10.137.32' cannot be found in any machine network"
Expected results:
network operator should not report error.
Additional info:
There is workaround is we can update the ELB ip cidr in infrastructures.config.openshift.io/cluster by manual.
- is duplicated by
-
OCPBUGS-42101 Error: API VIPs Not Found in Machine Network for UserManaged Load Balancer Configuration
- Closed
- links to