Network Operator Degraded After Installation When Using UserManaged LoadBalancer with Missing VIP Network in Machine Networks

Solution Verified - Updated -

Issue

  • When deploying an OpenShift cluster using the UserManaged LoadBalancer type[0], the installation fails. However, the cluster becomes available except for the network operator, which remains in a degraded state with the following error:
$ oc get co/network
NAME      VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
network   4.16.x    True        False         True       152m    Error while synchronizing spec and status of infrastructures.config.openshift.io/cluster: Error on validating API VIPs and Machine Networks: VIP 'x.x.x.x' cannot be found in any machine network

[0] Install-config.yaml:

platform:
  baremetal:
    apiVIPs:
      - <api_ip> 
    ingressVIPs:
      - <ingress> 
    loadBalancer:
      type: UserManaged

Environment

  • OpenShift 4.16.x
  • All platform
  • UserManaged LoadBalancer type
  • API VIPs and Ingress VIPs specified in the install configuration

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content