Bug 1961559

Summary:	[DOC][OCP47][BM][IPI] Missing step to configure provisioning IP address on provisioning host
Product:	OpenShift Container Platform	Reporter:	Rafal Szmigiel <rszmigie>
Component:	Documentation	Assignee:	Servesha <sdudhgao>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Omri Hochman <ohochman>
Severity:	urgent	Docs Contact:	Latha S <lmurthy>
Priority:	medium
Version:	4.7	CC:	aos-bugs, jokerman, kbon, lmurthy
Target Milestone:	---
Target Release:	4.6.z
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:	2022-01-05 02:49:22 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 Rafal Szmigiel 2021-05-18 09:18:38 UTC

Document URL: 
https://access.redhat.com/documentation/en-us/openshift_container_platform/4.7/html/installing/deploying-installer-provisioned-clusters-on-bare-metal#preparing-the-provisioner-node-for-openshift-install_ipi-install-installation-workflow

Section Number and Name: 
7.3.2. Preparing the provisioner node for OpenShift Container Platform installation

11. Configure networking.

Describe the issue: 
During BM IPI installation of OCP, openshift-baremetal-installer expects to have connectivity with Ironic via provisioning network (172.22.0.2). If there is no route to this address installation will fail as installator can't define BM hosts in Ironic. We should either add this information to the doc, advising to setup "provisioning" bridge IP address on provisioning host or consider use of apiVIP (so baremetal network) to reach Ironic's API.

Suggestions for improvement: 
add:
    nmcli connection modify provisioning ipv4.addresses 172.22.0.254/24 ipv4.method manual


Additional information: 

Personally I think we should be reaching Ironic over baremetal network. ApiVIP should be configured at quite early stage of deployment so we could use it as it is easy to predict (in opposite to primary IP address of bootstrap VM which is assigned by 3rd party DHCP).