Bug 1942827

Summary:	DHCP requirements for IPI on vShere misleading
Product:	OpenShift Container Platform	Reporter:	David Juran <djuran>
Component:	Documentation	Assignee:	Neal Alhadeff <nalhadef>
Status:	CLOSED DUPLICATE	QA Contact:	jima
Severity:	medium	Docs Contact:	Latha S <lmurthy>
Priority:	medium
Version:	4.7	CC:	aos-bugs, clasohm, hgomes, jima, lmurthy, nalhadef, oarribas, zzhao
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-04-01 15:31:53 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 David Juran 2021-03-25 05:49:52 UTC

Document URL: 
https://docs.openshift.com/container-platform/4.7/installing/installing_vsphere/installing-vsphere-installer-provisioned-network-customizations.html#installation-vsphere-infrastructure_installing-vsphere-installer-provisioned-network-customizations

Section Number and Name: 
Networking requirements

Describe the issue: 
The current wording implies that static DHCP records must be provided for the VMs ahead of time. This is however not practical as the MAC address of the VMs are not known before the installation starts.

Suggestions for improvement: 
What should be described is that a DHCP range must be allocated for the cluster VMs and after the installation, it is recommended that the allocations should be changed to a static reservation in the DHCP server though a manual procedure.

Comment 12 zhaozhanqi 2022-02-11 09:11:26 UTC

@jima assign to you for help acking since it's duplicated with https://bugzilla.redhat.com/show_bug.cgi?id=1900784

Comment 13 jima 2022-02-11 10:19:55 UTC

we only hit the issue when upgrading from 4.5 to 4.6 until now, so need to reserve static ip of control node on running 4.5 cluster before upgrading to 4.6.

Comment 14 Neal Alhadeff 2022-02-11 12:13:45 UTC

@lmurthy, 4.6 is covered separately in https://bugzilla.redhat.com/show_bug.cgi?id=1900784.

Thanks,@jima@redhat and @zzhao@redhat. I will not carry this beyond 4.7.

Comment 17 Neal Alhadeff 2022-04-01 15:31:53 UTC

Closed. Duplicate of BZ1900784.
https://bugzilla.redhat.com/show_bug.cgi?id=1900784

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

Comment 18 Red Hat Bugzilla 2023-09-15 01:04:00 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days