# w3m -dump -cols 200 'https://search.ci.openshift.org/?search=timed+out+waiting+for+cluster+to+acknowledge+upgrade&maxAge=48h&context=1&type=junit&name=&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job'|grep 'failures match' release-openshift-origin-installer-e2e-aws-upgrade-4.5-to-4.6-to-4.7-to-4.8-ci (all) - 3 runs, 100% failed, 33% of failures match = 33% impact -> v4.5.39 which did not included the fix pr periodic-ci-openshift-release-master-ci-4.5-upgrade-from-stable-4.4-e2e-azure-ovn-upgrade (all) - 8 runs, 88% failed, 14% of failures match = 13% impact -> v4.4 to v4.5 upgrade release-openshift-origin-installer-e2e-gcp-ovn-upgrade-4.5-stable-to-4.6-ci (all) - 8 runs, 100% failed, 13% of failures match = 13% impact -> v4.5.39 which did not included the fix pr release-openshift-origin-installer-e2e-aws-upgrade (all) - 11 runs, 18% failed, 50% of failures match = 9% impact -> v4.5.39 which did not included the fix pr According to above result, move the bug to verify.
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.5.40 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-2021:2056