Known issue for vSphere IPI upgrades

[codyhoag]

No description provided.

[openshift-docs-preview-bot]

The preview will be available shortly at:

• https://rn-4-6-bz1883521--ocpdocs.netlify.com/

[codyhoag]

@jinyunma PTAL. Thanks!

[jinyunma]

It's better to reword the description and add more details, something like below:
When upgrading a cluster from version 4.5 to 4.6 that was installed with installer-provisioned infrastructure on vSphere, in case control plane nodes' IPs are changed during upgrading which lead to upgrade failed, please reserve them before upgrading to 4.6. You can do this on the DHCP server by adding the IPs into the /etc/dhcp/dhcpd.conf file and then restarting dhcpd process.

[codyhoag]

@jcpowermac what are your thoughts on adding more details, as @jinyunma suggested? I want to make sure I'm considering the points you brought up yesterday. How about something like this:

When upgrading a cluster from version 4.5 to 4.6 that was installed with installer-provisioned
infrastructure on vSphere, the upgrade fails if the control plane node IPs change during the
upgrade. As a workaround, you must reserve the control plane node IPs before upgrading to
version 4.6. You can do this by adding the IPs into the `/etc/dhcp/dhcpd.conf` file on the DHCP
server and then restarting the DHCP daemon process.

[jcpowermac]

You can do this by adding the IPs into the /etc/dhcp/dhcpd.conf file on the DHCP
server and then restarting the DHCP daemon process.

If it can be less Linux (RHEL) specific. We don't know which DHCP server the customer is using.