DNS VIP is no longer needed, and is not in use to form the etcd cluster. - remove it from installconfig, ignore if passed - remove it from platform - remove the wizard question for dns_vip - remove from platform documents under docs/user/ovirt
also remove the openshift/api struct field - https://github.com/openshift/api/blob/95abe2d2f4223d5931e418bf8e4d3773d16b42c0/config/v1/types_infrastructure.go#L397
due to capacity constraints we will be revisiting this bug in the upcoming sprint
(In reply to Roy Golan from comment #1) > also remove the openshift/api struct field - > https://github.com/openshift/api/blob/ > 95abe2d2f4223d5931e418bf8e4d3773d16b42c0/config/v1/types_infrastructure. > go#L397 We cannot remove this field at this moment, otherwise will break the API compatibility. In one year from now, we will able to do that (for all platforms).
We don't want to immediately remove the field because that can cause upgraded clusters to fail. Instead, we should update the API doc to deprecate the field and indicate that the value is no longer set and no longer honored. This leaves old clusters with previous value set, but ensures that new clusters cannot make use of it. One year from now, we can reassess removal or force clearing of the value to bring every cluster in line.
Verified with 4.6.0-0.nightly-2020-09-28-212756 Verification steps: 1. Check https://github.com/openshift/installer/blob/master/docs/user/ovirt/install_ipi.md to see if the reference to DNS VIP has been removed 2. Run openshift-install create install-config and go through the wizard. Make sure it does not ask for DNS VIP.
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 (OpenShift Container Platform 4.6 GA Images), 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:4196