Version: 4.7.z Platform: VMware UPI What happened? For 4.7 vSphere UPI CI jobs, nodes are not applying IP address configuration via Afterburn. If nodes have an issue retrieving an IP from DHCP, installs appear to be stalling during ignition and the node is not pingable via the IP given in ignition. A simple reboot of the node enables ignition to continue and the node is pingable at the intended IP. This issue applies to 4.6 and 4.7 UPI installs in CI. In 4.8, which applies the IP via Afterburn, this issue does not occur.
use upstream terraform scripts to install ocp 4.8.0-0.nightly-2021-06-22-192915 on VMC, installation is completed. $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.8.0-0.nightly-2021-06-22-192915 True False 30m Cluster version is 4.8.0-0.nightly-2021-06-22-192915 $ oc get nodes NAME STATUS ROLES AGE VERSION compute-0 Ready worker 43m v1.21.0-rc.0+120883f compute-1 Ready worker 43m v1.21.0-rc.0+120883f control-plane-0 Ready master 114m v1.21.0-rc.0+120883f control-plane-1 Ready master 114m v1.21.0-rc.0+120883f control-plane-2 Ready master 114m v1.21.0-rc.0+120883f move bug to VERIFIED.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:2438