This is a clone of Bug #1826861. This is the description of that bug:
This bug was initially created as a copy of Bug #1780698
I am copying this bug because:
Description of problem:
I have a cluster that was on 4.1.23 (upgraded continuously from about 4.1.4).
The upgrade to either 4.1.24 or 4.1.25 fails with a download error:
info: An upgrade is in progress. Unable to apply 4.1.25: could not download the update
oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.1.23 True True 44h Unable to apply 4.1.25: could not download the update
All Cluster Operators show on 4.1.23.
oc adm must-gather is at https://drive.google.com/open?id=18mqD6BpEwAQbApb1_5MD9j-cMBckBIA6
I can provide a kubeconfig as well to poke around there.
Awaiting cherry-pick approval from patch manager
Verified on clusterlogging.4.3.20-202005141057
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.