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

Bug 1831382

Summary:	RHV IPI install needs to clarify the IP addresses used for the openshift-installer configuration
Product:	OpenShift Container Platform	Reporter:	Steven Ellis <sellis>
Component:	Installer	Assignee:	Steve Goodman <sgoodman>
Installer sub component:	OpenShift on RHV	QA Contact:	Michael Burman <mburman>
Status:	CLOSED DUPLICATE	Docs Contact:	ctomasko <ctomasko>
Severity:	low
Priority:	low	CC:	aos-bugs, ctomasko, gzaidman, jokerman, jwarnica, mrhodes
Version:	4.4	Keywords:	Documentation
Target Milestone:	---
Target Release:	4.8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-05-05 07:22:25 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:

Description Steven Ellis 2020-05-05 03:20:49 UTC

Document URL: 

https://docs.openshift.com/container-platform/4.4/installing/installing_rhv/installing-rhv-default.html#installing-rhv-preparing-the-network-environment_installing-rhv-default

Section Number and Name: 

Creating the installation configuration file

Describe the issue: 

It isn't clear how the reserved IP addresses (api.domain api-int.domain) map onto the API and DNS VIPs

Suggestions for improvement: 

In the section "Preparing the network environment on RHV" and the section "Creating the installation configuration file" have consistent descriptions of the VIPs.

Currently api.domain would be the DNS VIP, and api-int would be the API VIP.

Additional information:

Comment 3 Steve Goodman 2021-05-05 07:22:25 UTC

Closing this as a duplicate of bug 1893182, which I have addressed in the following PR:

https://github.com/openshift/openshift-docs/pull/32189

NOTE: This bug was opened on version 4.4. We are addressing only as far back as 4.6. So this PR addresses 4.6, 4.7 and 4.8.

*** This bug has been marked as a duplicate of bug 1893182 ***