This is still affecting 4.7 as well as 4.7 -> 4.8 upgrades: https://search.ci.openshift.org/?maxAge=168h&context=1&type=bug%2Bjunit&name=4.8&maxMatches=5&maxBytes=20971520&groupBy=job&search=%5C%5Bsig-cluster-lifecycle%5C%5D+cluster+upgrade+should+be+fast
Not much we can do here without some master-ward progress besides bumping the origin timeout.
We back port the fix for https://bugzilla.redhat.com/show_bug.cgi?id=1942164 i.e.increase in timeout to 90mins.
The test script PR looks good to me, and merged now.
But I searched "cluster upgrade should complete in 90" in https://search.ci.openshift.org/?search=cluster+upgrade+should+complete+in+90&maxAge=168h&context=1&type=all&name=&excludeName=&maxMatches=1&maxBytes=20971520&groupBy=job&wrap=on
There is no matched job history yet (filter: "4.7->4.8"/"4.8.n -> 4.8.n+1" + non-aws + OVN) for a final confirm.
I will wait for some more time to check.
Okay. I found one job to validate this change.
In the passed test cases, "[sig-cluster-lifecycle] cluster upgrade should complete in 90.00 minutes" is seen there.
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.8.24 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.