Hide Forgot
Hi All, Just checking in to see how things are going to so we can update the customer. Thank you for any information you can provide. Darren Carpenter
Held up by 2094765, which was held up by 2118609 backport to 4.9 (tracked in JIRA) that is now moving forward with https://github.com/openshift/machine-config-operator/pull/3180
Verified on 4.7.0-0.nightly-2022-10-17-061132 libvirt IPI DHCP bonding, reboots successful. AWS IPI scaled to 30 nodes, reboots successful. NAME STATUS ROLES AGE VERSION ip-10-0-129-99.compute.internal Ready worker 72m v1.20.15+98b2293 ip-10-0-132-108.compute.internal Ready worker 20m v1.20.15+98b2293 ip-10-0-141-201.compute.internal Ready worker 19m v1.20.15+98b2293 ip-10-0-144-148.compute.internal Ready worker 20m v1.20.15+98b2293 ip-10-0-145-65.compute.internal Ready worker 20m v1.20.15+98b2293 ip-10-0-150-150.compute.internal Ready worker 20m v1.20.15+98b2293 ip-10-0-155-133.compute.internal Ready worker 19m v1.20.15+98b2293 ip-10-0-155-142.compute.internal Ready worker 20m v1.20.15+98b2293 ip-10-0-158-74.compute.internal Ready worker 20m v1.20.15+98b2293 ip-10-0-159-114.compute.internal Ready master 82m v1.20.15+98b2293 ip-10-0-175-255.compute.internal Ready worker 20m v1.20.15+98b2293 ip-10-0-177-169.compute.internal Ready worker 20m v1.20.15+98b2293 ip-10-0-178-34.compute.internal Ready worker 20m v1.20.15+98b2293 ip-10-0-180-209.compute.internal Ready worker 71m v1.20.15+98b2293 ip-10-0-181-254.compute.internal Ready worker 20m v1.20.15+98b2293 ip-10-0-184-15.compute.internal Ready worker 20m v1.20.15+98b2293 ip-10-0-186-188.compute.internal Ready worker 20m v1.20.15+98b2293 ip-10-0-188-158.compute.internal Ready worker 20m v1.20.15+98b2293 ip-10-0-190-29.compute.internal Ready master 86m v1.20.15+98b2293 ip-10-0-190-96.compute.internal Ready worker 20m v1.20.15+98b2293 ip-10-0-194-48.compute.internal Ready worker 19m v1.20.15+98b2293 ip-10-0-196-49.compute.internal Ready worker 20m v1.20.15+98b2293 ip-10-0-196-97.compute.internal Ready worker 19m v1.20.15+98b2293 ip-10-0-200-147.compute.internal Ready worker 20m v1.20.15+98b2293 ip-10-0-202-119.compute.internal Ready worker 19m v1.20.15+98b2293 ip-10-0-202-64.compute.internal Ready worker 20m v1.20.15+98b2293 ip-10-0-206-243.compute.internal Ready worker 20m v1.20.15+98b2293 ip-10-0-218-208.compute.internal Ready worker 71m v1.20.15+98b2293 ip-10-0-219-50.compute.internal Ready master 86m v1.20.15+98b2293 ip-10-0-223-6.compute.internal Ready worker 20m v1.20.15+98b2293
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 (OpenShift Container Platform 4.7.60 bug fix 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/RHBA-2022:7302