Description of problem: The baremetal platform no longer uses the DNS VIP, thanks to changes in the way etcd clustering works. However, there is still a DNS VIP item in the baremetal install-config in the installer. Worse, it is a mandatory setting because previously the install could not complete without it. We need to remove that setting. Version-Release number of selected component (if applicable): 4.5 How reproducible: Always Steps to Reproduce: 1. Run baremetal install without setting DNS VIP in install-config Actual results: The install-config validations will fail. Expected results: Deployment proceeds normally. Additional info: DNS VIP usage was removed in https://github.com/openshift/machine-config-operator/pull/1569
*** Bug 1840512 has been marked as a duplicate of this bug. ***
(ocp-edge-qe-venv) [root@titan44 linchpin-workspace]# oc version Client Version: 4.5.0-202005291417-9933eb9 Needs manual installation. Once the install-config.yaml has been created on the provisionhost, I've deleted the dnsVIP record & let the installation to continue. The deployment was successful.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, 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/RHBA-2020:2409