Description of problem:
Run "oc adm upgrade --to-latest=true" to manually update current cluster to latest available version, but it dose not choose the actual "latest" version in the list.
Checked 4.1 nightly builds on https://openshift-release.svc.ci.openshift.org/, the top three is as following(4.1.0-0.nightly-2019-05-22-190823 should be latest):
Name Phase Started Tests Upgrades
4.1.0-0.nightly-2019-05-22-190823 Accepted 13 hours ago aws aws-serial 4.1.0-rc.5
4.1.0-0.nightly-2019-05-22-050858 Accepted 1 day ago aws aws-serial 4.1.0-rc.5
4.1.0-0.nightly-2019-05-21-060354 Accepted 2 days ago aws aws-serial 4.1.0-rc.5
[root@preserve-jliu-worker 20190523_15261]# ./oc adm upgrade
Cluster version is 4.1.0-rc.5
[root@preserve-jliu-worker 20190523_15261]# ./oc adm upgrade --to-latest=true
Updating to latest version 4.1.0-0.nightly-2019-05-22-050858
[root@preserve-jliu-worker 20190523_15261]# oc get clusterversion -o json|jq ".items.spec"
Version-Release number of the following components:
Steps to Reproduce:
1. Run "# ./oc adm upgrade --to-latest=true" to update current cluster to latest available version(there should be more than 1 payload in the list)
"--to-latest=true" did not update cluster to latest available version
Should choose the latest build as desiredUpdate
Please attach logs from ansible-playbook with the -vvv flag
Good catch. There's a missing != here . I'll file a fix in a few hours if nobody else has time before that ;).
This was eating at me, so I just went ahead and worked up the master PR: https://github.com/openshift/origin/pull/22893 Bot will cherry-pick back to 4.1 when the master PR lands.
4.1 backport: https://github.com/openshift/origin/pull/22897
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.