Bug 1537388 - Global flag --version is not respected
Summary: Global flag --version is not respected
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: oc
Version: 3.9.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: 3.10.0
Assignee: Maciej Szulik
QA Contact: Xingxing Xia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-23 05:20 UTC by Xingxing Xia
Modified: 2019-03-14 02:15 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-14 02:15:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:0405 0 None None None 2019-03-14 02:15:41 UTC

Description Xingxing Xia 2018-01-23 05:20:20 UTC
Description of problem:
`oc options`, `oc adm options` now has new flag --version:
$ oc options
...
      --version=false: Print version information and quit
...

But the flag is not respected in any command, confusing user what it is used for.

Version-Release number of selected component (if applicable):
v3.9.0-0.22.0

How reproducible:
Always

Steps to Reproduce:
1. Login to openshift, create project
2. Run any commands with global flag --version=true or false
$ oc get pod --version=true
No resources found.

$ oc get pod --version=false
No resources found.

Actual results:
2. Same result when with --version=true or false. --version is not respected

Expected results:
2. It is respected, result of --version=true or false should have difference per  above help info "Print version information and quit"

Additional info:

Comment 4 errata-xmlrpc 2019-03-14 02:15:34 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-2019:0405


Note You need to log in before you can comment on or make changes to this bug.