*** Bug 1876237 has been marked as a duplicate of this bug. ***
Saw this typo in `oc` 4.5.7
$ oc version
Client Version: 4.5.7
Server Version: 4.5.8
Kubernetes Version: v1.17.1+a1af596
$ oc adm upgrade --allow-explicit-upgrade --to-image quay.io/openshift-release-dev/ocp-release@sha256:ae61753ad8c8a26ed67fa233eea578194600d6c
warning: The requested upgrade image is not one of the available updates. You have used --allow-explicit-upgrade to the update to preceed anyway
error: already upgrading.
PR in the queue
Verified bug in the payload below and i do not see the typo as reported in the bug.
[ramakasturinarra@dhcp35-60 openshift-client-linux-4.5.0-0.nightly-2020-09-12-063044]$ ./oc version
Client Version: 4.5.0-0.nightly-2020-09-12-063044
Server Version: 4.5.0-0.nightly-2020-09-12-063044
Kubernetes Version: v1.18.3+6c42de8
[ramakasturinarra@dhcp35-60 openshift-client-linux-4.5.0-0.nightly-2020-09-12-063044]$ ./oc adm upgrade --to-image=registry.svc.ci.openshift.org/ocp/release:4.5.0-0.nightly-2020-09-12-063044 --force=true --allow-explicit-upgrade=true
warning: Using by-tag pull specs is dangerous, and while we still allow it in combination with --force for backward compatibility, it would be much safer to pass a by-digest pull spec instead
warning: The requested upgrade image is not one of the available updates. You have used --allow-explicit-upgrade to the update to proceed anyway
warning: --force overrides cluster verification of your supplied release image and waives any update precondition failures.
Updating to release image registry.svc.ci.openshift.org/ocp/release:4.5.0-0.nightly-2020-09-12-063044
Based on the above moving the bug to verified state.
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.5.11 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.