+++ This bug was initially created as a clone of Bug #2111467 +++ Description of problem: For a Power VS machine when it fails to fetch the internal IP from DHCP server, Its skipping to set the Node Internal DNS address for machine, This leads to csr being not approved and machine never becomes node. Version-Release number of selected component (if applicable): 4.11
Awaiting new 4.11 RC build to verify this.
Verified with OCP 4.11.0, Post-deployment, no CSR was pending and the cluster was healthy # oc get nodes -owide NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME rdr-ipi-fra1-6-pravin-v68tr-master-0 Ready master 5d21h v1.24.0+9546431 192.168.0.10 192.168.0.10 Red Hat Enterprise Linux CoreOS 411.86.202208022159-0 (Ootpa) 4.18.0-372.19.1.el8_6.ppc64le cri-o://1.24.1-11.rhaos4.11.gitb0d2ef3.el8 rdr-ipi-fra1-6-pravin-v68tr-master-1 Ready master 5d21h v1.24.0+9546431 192.168.0.11 192.168.0.11 Red Hat Enterprise Linux CoreOS 411.86.202208022159-0 (Ootpa) 4.18.0-372.19.1.el8_6.ppc64le cri-o://1.24.1-11.rhaos4.11.gitb0d2ef3.el8 rdr-ipi-fra1-6-pravin-v68tr-master-2 Ready master 5d21h v1.24.0+9546431 192.168.0.12 192.168.0.12 Red Hat Enterprise Linux CoreOS 411.86.202208022159-0 (Ootpa) 4.18.0-372.19.1.el8_6.ppc64le cri-o://1.24.1-11.rhaos4.11.gitb0d2ef3.el8 rdr-ipi-fra1-6-pravin-v68tr-worker-5dq8w Ready worker 5d21h v1.24.0+9546431 192.168.0.15 192.168.0.15 Red Hat Enterprise Linux CoreOS 411.86.202208022159-0 (Ootpa) 4.18.0-372.19.1.el8_6.ppc64le cri-o://1.24.1-11.rhaos4.11.gitb0d2ef3.el8 rdr-ipi-fra1-6-pravin-v68tr-worker-6cnpt Ready worker 5d21h v1.24.0+9546431 192.168.0.14 192.168.0.14 Red Hat Enterprise Linux CoreOS 411.86.202208022159-0 (Ootpa) 4.18.0-372.19.1.el8_6.ppc64le cri-o://1.24.1-11.rhaos4.11.gitb0d2ef3.el8 rdr-ipi-fra1-6-pravin-v68tr-worker-d2zbx Ready worker 5d21h v1.24.0+9546431 192.168.0.16 192.168.0.16 Red Hat Enterprise Linux CoreOS 411.86.202208022159-0 (Ootpa) 4.18.0-372.19.1.el8_6.ppc64le cri-o://1.24.1-11.rhaos4.11.gitb0d2ef3.el8 # oc get csr No resources found
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.11.1 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-2022:6103