help description for oc adm upgrade warns: --to-image='': Provide a release image to upgrade to. WARNING: This option does not check for upgrade compatibility and may break your cluster. this warning however became incorrect since the introduction of --allow-explicit-upgrade How reproducible: 100% Steps to Reproduce: oc adm upgrade --help | grep " --to-image=''" Actual results: --to-image='': Provide a release image to upgrade to. WARNING: This option does not check for upgrade compatibility and may break your cluster. Expected results: the help message should be according to the functionality
Reproducing: Client Version: 4.11.0-0.nightly-2022-03-13-055724 <-snip-> If there are no versions available, or a bug in the cluster version operator prevents updates from being retrieved, the more powerful and dangerous --to-image=IMAGE option may be used. This instructs the cluster to upgrade to the contents of the specified release image, regardless of whether that upgrade is safe to apply to the current version. </-snip-> <-snip-> --to-image='': Provide a release image to upgrade to. WARNING: This option does not check for upgrade compatibility and may break your cluster. </-snip-> Verifying: Client Version: 4.11.0-0.nightly-2022-03-15-223029 <-snip-> If there are no versions available, or a bug in the cluster version operator prevents updates from being retrieved, --to-image may be combined with the more powerful and dangerous --allow-explicit-upgrade. This instructs the cluster to upgrade to the contents of the specified release image, regardless of whether that upgrade is known to be recommended for the current version. </-snip-> <-snip-> --to-image='': Provide a release image to upgrade to. </-snip-> as expected!
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 (Important: OpenShift Container Platform 4.11.0 bug fix and security 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. https://access.redhat.com/errata/RHSA-2022:5069