Description of problem: With https://bugzilla.redhat.com/show_bug.cgi?id=1756454 merged oc adm upgrade --force is now used to allow upgrade when content validation fails. The help for the --force option does not describe this behavior - the help is basically the same as the for the new --allow-upgrade-with-warnings option" --allow-upgrade-with-warnings=false: Upgrade even if an upgrade is in process or a cluster error is blocking the update. --force=false: Upgrade even if an upgrade is in process or other error is blocking update. Version-Release number of selected component (if applicable): 4.2.0-0.nightly-2019-10-07-011045 How reproducible: Always
Disregard comment 1 - wrong bz.
Confirmed with oc version, the issue has fixed: [root@dhcp-140-138 oc-client]# oc version Client Version: v4.3.0 [root@dhcp-140-138 oc-client]# oc adm upgrade -h Upgrade the cluster to a newer version ...... --force=false: Forcefully upgrade the cluster even when upgrade release image validation fails and the cluster is reporting errors.
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:0062