Bug 1759185

Summary:	Help for oc adm upgrade --force option does not describe new behavior
Product:	OpenShift Container Platform	Reporter:	Mike Fiedler <mifiedle>
Component:	oc	Assignee:	Maciej Szulik <maszulik>
Status:	CLOSED ERRATA	QA Contact:	zhou ying <yinzhou>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.2.0	CC:	aos-bugs, jokerman, mfojtik
Target Milestone:	---
Target Release:	4.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-13 21:27:07 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Mike Fiedler 2019-10-07 14:49:29 UTC

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

Comment 2 Mike Fiedler 2019-10-07 15:51:01 UTC

Disregard comment 1 - wrong bz.

Comment 4 zhou ying 2019-11-18 00:57:58 UTC

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.

Comment 6 errata-xmlrpc 2020-05-13 21:27:07 UTC

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