We should sort the available updates with the most recent first.
Merged way back on July 11th . No idea why the Bugzilla bot didn't mark this MODIFIED when the PR landed. Checking 4.2 RCs:
$ oc adm release info --commits quay.io/openshift-release-dev/ocp-release:4.2.0-rc.1 | grep console
console https://github.com/openshift/console 4add1e0a27ec21af3ff460d657852f1fba36f3fe
$ git log --oneline 4add1e0a27ec21af3ff460d657852f1fba36f3fe | grep bf925a3fa
bf925a3fa Sort updates most recent first in cluster update modal
So I'm moving this to ON_QA.
Back to MODIFIED so ARTs sweeper will put these in errata.
Setuped a ocp 4.2 env with payload 4.2.0-0.ci-2019-10-07-080755. Checked on cluster setting page, in the update dropdown list, the available updates are sorted by time, the latest update is at top.
The bug has been fixed, move it Verified.
Created attachment 1623432 [details]
expected dropdown list
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.