Bug 1956678 - DNS VIP is requested by installer in RHV IPI 4.5
Summary: DNS VIP is requested by installer in RHV IPI 4.5
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.5
Hardware: x86_64
OS: Linux
Target Milestone: ---
: ---
Assignee: OCP on RHV Team
QA Contact: Michael Burman
Depends On:
TreeView+ depends on / blocked
Reported: 2021-05-04 08:27 UTC by Jatan Malde
Modified: 2021-05-10 12:48 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-05-10 12:48:33 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Jatan Malde 2021-05-04 08:27:37 UTC

Hello Team, IHAC installing OCP 4.5.27 using IPI format on RHV 4.4 and as we know dns VIP is taken out from 4.5, the installer still asks for the value and if taken out from the install-config, it report error while creating manifests or cluster from the config.

[root@svc ocp_rhv]# ./openshift-install version
./openshift-install 4.5.27
built from commit b42b0475e12c6e5b8536b3aa53b5db3f6970e1de
release image quay.io/openshift-release-dev/ocp-release@sha256:412276155bfe186c35322a788321ebf110130a272e18f55a1a2510f15ee0bb04

On removing dns_vip: installation cannot proceed:
[root@svc ocp_rhv]# ./openshift-install create cluster --dir=/home/manish/ocp_rhv --log-level=info
FATAL failed to fetch Metadata: failed to load asset "Install Config": invalid "install-config.yaml" file: platform.ovirt.dns_vip: Invalid value: "": "" is not a valid IP

Althought the cluster installation is correctly done, no issue with it, the installation does not use the dnsVIP and each node gets it own ip in the /etc/resolv.conf file. All the issue stands is installer should not ask for DNS VIP if it has been taken out of action. 

additional details:-

What happened?

What did you expect to happen?

#Enter text here.

How to reproduce it (as minimally and precisely as possible)?

$ your-commands-here

Anything else we need to know?

#Enter text here.

Comment 1 Gal Zaidman 2021-05-10 12:48:33 UTC
This is a known issue that we are not planing on fixing, 4.5 will be EOL soon and because the fix is complex, relevant to only new installations (we don't expect new installations of 4.5) and is only cosmetic since you can give any IP and it will not be used anyway I'm closing this as a won't fix

Note You need to log in before you can comment on or make changes to this bug.