Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1840496

Summary:	Baremetal DNS VIP is no longer used
Product:	OpenShift Container Platform	Reporter:	Ben Nemec <bnemec>
Component:	Installer	Assignee:	Ben Nemec <bnemec>
Installer sub component:	OpenShift on Bare Metal IPI	QA Contact:	Nataf Sharabi <nsharabi>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	high	CC:	augol, rfreiman, vvoronko
Version:	4.5	Keywords:	Triaged
Target Milestone:	---
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	Feature: install-config simplification Reason: Due to some changes in how baremetal deployment works, it was no longer necessary to use a DNS VIP. Removing this requirement improves the install experience as it eliminates a mandatory configuration option. Result: It is easier to deploy on baremetal.	Story Points:	---
Clone Of:
Clones:	1841066 1843010 (view as bug list)		Environment:
Last Closed:	2020-07-13 17:41:51 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1843010

Description Ben Nemec 2020-05-27 03:45:17 UTC

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

Comment 1 Steven Hardy 2020-05-27 09:06:07 UTC

*** Bug 1840512 has been marked as a duplicate of this bug. ***

Comment 4 Nataf Sharabi 2020-06-08 21:31:13 UTC

(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.

Comment 5 errata-xmlrpc 2020-07-13 17:41:51 UTC

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