Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1595669

Summary: Restore -v in set deployment-hook and status commands
Product: OpenShift Container Platform Reporter: Maciej Szulik <maszulik>
Component: ocAssignee: Maciej Szulik <maszulik>
Status: CLOSED ERRATA QA Contact: zhou ying <yinzhou>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.11.0CC: aos-bugs, jokerman, mmccomas, xxia
Target Milestone: ---   
Target Release: 3.11.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: 2018-10-11 07:20:43 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 Maciej Szulik 2018-06-27 10:30:34 UTC
As part of the 1.11 rebase (#20033) we've dropped -v support in oc set deployment-hook and oc status commands we need to restore them back.

Comment 1 Maciej Szulik 2018-07-24 19:38:01 UTC
PR in-flight: https://github.com/openshift/origin/pull/20412

Comment 2 Xingxing Xia 2018-07-31 06:29:22 UTC
$ oc status -v -n xxia-proj
Flag shorthand -v has been deprecated, Use --suggest instead.  Will be dropped in a future release
Flag --v has been deprecated, Use --suggest instead.  Will be dropped in a future release
...

$ oc set deployment-hook dc/ruby-ex --pre -v myvolume -- /bin/true
Flag shorthand -v has been deprecated, Use --volumes instead.
Flag --v has been deprecated, Use --volumes instead.  Will be dropped in a future release
...

The second line about --v "Flag --v has been deprecated ..." needs be removed. 

Besides, -v is still showing in `oc options`: -v, --v=0: log level for V logs This causes issue:
$ oc status --v=6
Error: invalid argument "6" for "--v" flag: strconv.ParseBool: parsing "6": invalid syntax

If this bug wants to restore -v in oc status and oc set deployment-hook, -v should be removed from `oc options`

Comment 3 Xingxing Xia 2018-07-31 06:32:20 UTC
`oc set deployment-hook -h` has some examples of `oc set deployment-hook ... -v`, it's better to replace them with --volumes BTW. Thanks.

Comment 4 Maciej Szulik 2018-07-31 10:34:17 UTC
Fixes in https://github.com/openshift/origin/pull/20481

Comment 5 Xingxing Xia 2018-08-06 09:33:12 UTC
Checked in oc v3.11.0-0.11.0, comment 3 is fixed.
The comment 2 issue still exists. Seems comment 2's fix is missed in the new PR, could you PTAL?

Comment 6 Maciej Szulik 2018-08-09 11:41:40 UTC
Yeah, you're right, fix is in https://github.com/openshift/origin/pull/20582.

Comment 7 openshift-github-bot 2018-08-13 15:53:46 UTC
Commit pushed to master at https://github.com/openshift/origin

https://github.com/openshift/origin/commit/875f246288331c9e3acc861f3c2447f72db6963b
Merge pull request #20582 from soltysh/bug1595669

Bug 1608254 - update help messages

Comment 8 Xingxing Xia 2018-08-16 06:59:47 UTC
Checked oc v3.11.0-0.16.0, the beginning half part of comment 2 about `oc status/set ... -v ...` showing irrelevant 'Flag --v' is fixed.
But the ending half part of comment 2 still exists about:
`oc options` displaying '-v, --v=0' where -v is included.
`oc status --v=6` showing Error: invalid argument ...
Please help check again.

Comment 9 Maciej Szulik 2018-08-20 11:47:14 UTC
oc options is global, the --v is fixed and different only for set deployment-hook and status commands. It will disappear eventually and then oc options output will make sense.

Comment 10 Xingxing Xia 2018-08-21 01:58:56 UTC
OK, though it is a bit imperfect. Verified

Comment 12 errata-xmlrpc 2018-10-11 07:20:43 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-2018:2652