Hide Forgot
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.149 Safari/537.36 Build Identifier: When the Last Completed Version of a cluster is not found in the update service, an error is reported on the console. This is actually not an error with the cluster itself but a [possibly] missing version in the upgrade service itself. Reproducible: Always Steps to Reproduce: 1. Install cluster from a nightly build 2. Examine Administration > Cluster Settings 3. Update Status will show 'Error Retrieving' Actual Results: 'Error Retrieving' Expected Results: Cluster should report 'Version Not Found' or 'Upgrade Not Available' instead of reporting an error as it's not an error with the cluster itself.
So unable to find the version of the cluster in update service is most definitely an error. Because that blocks CVO functionality to fetch the available updates for upgrade.. that is core to the openshift. So moving to console team to either show that error differently if they like, so close this BZ.
I think there is a distinction though that wasn't clear from what I wrote. Not finding a version that IS in the update service would be an error (i.e. network/system outage, something else), but is NOT finding a version that IS NOT in the update service also the same error? I don't think they are the same. Perhaps it is simply a distinction made at the UI, but the CVO would need to make that distinction for the UI to also be aware.
Moving to upcoming sprint as there are many bugs.
Checked on OCP 4.5 cluster with payload 4.5.0-0.nightly-2020-05-13-202437. Go to Administration > Cluster Settings page, the channel is "stable-4.5", and "Update Status" shows "Version not found", hover on it, there is info: Unable to retrieve available updates: currently installed version 4.5.0-0.nightly-2020-05-13-202437 not found in the "stable-4.5" channel. The bug is fixed.
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. https://access.redhat.com/errata/RHBA-2020:2409