Bug 1532520

Summary: fix vdsm-client documentation
Product: [oVirt] vdsm Reporter: Irit Goihman <igoihman>
Component: Bindings-APIAssignee: Irit Goihman <igoihman>
Status: CLOSED CURRENTRELEASE QA Contact: Lucie Leistnerova <lleistne>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.19.26CC: bugs, lleistne, lveyde
Target Milestone: ovirt-4.1.9Flags: rule-engine: ovirt-4.1+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: vdsm v4.19.45 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-01-24 10:40:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Irit Goihman 2018-01-09 08:31:57 UTC
vdsm-client man page and documentation examples of using JSON file are not correct.
The '-f' flag that points to a JSON file that contains the arguments should be specified before the namespace.

Comment 1 Lucie Leistnerova 2018-01-12 13:03:55 UTC
The documentation is not changed, there is still in examples:

vdsm-client Lease info -f lease.json

cat <<EOF | vdsm-client Lease info -f -


Tested in vdsm-client-4.19.44-1.el7ev.noarch

Comment 2 Irit Goihman 2018-01-14 12:23:59 UTC
Lucie, which file are you looking at? I think this change wasn't added to the build.

Comment 3 Lucie Leistnerova 2018-01-15 07:59:00 UTC
man vdsm-client and file /usr/lib/python2.7/site-packages/vdsmclient/client.py

Comment 4 Lucie Leistnerova 2018-01-17 14:09:15 UTC
documentation fixed

verified in vdsm-client-4.19.45-1.el7ev.noarch

Comment 5 Sandro Bonazzola 2018-01-24 10:40:53 UTC
This bugzilla is included in oVirt 4.1.9 release, published on Jan 24th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.1.9 release, published on Jan 24th 2018, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.