RHOCP 4.x installation fails when apiVIP and ingressVIP values are set as FQDN

Solution Verified - Updated -

Issue

  • When FQDN values are mentioned for apiVIP and ingressVIP in install-config.yaml file, the openshift-install command fails with an error:
$ openshift-baremetal-install --dir ~/clusterconfigs create cluster
FATAL failed to fetch Metadata: failed to load asset "Install Config": invalid "install-config.yaml" file: [platform.baremetal.apiVIP: Invalid value: "api.cluster.example.com": "api.cluster.example.com" is not a valid IP, platform.baremetal.apiVIP: Invalid value: "api.cluster.example.com": IP expected to be in one of the machine networks: 192.168.234.0/24,fc00:0:c0ff:ee::/64,
platform.baremetal.ingressVIP: Invalid value: "test.apps.cluster.example.com": "test.apps.cluster.example.com" is not a valid IP, platform.baremetal.ingressVIP: Invalid value: "test.apps.cluster.example.com": IP expected to be in one of the machine networks: 192.168.234.0/24,fc00:0:c0ff:ee::/64]

Environment

  • Red Hat Openshift Container Platform 4.x

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