Bug 1532520 - fix vdsm-client documentation
Summary: fix vdsm-client documentation
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: vdsm
Classification: oVirt
Component: Bindings-API
Version: 4.19.26
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ovirt-4.1.9
: ---
Assignee: Irit Goihman
QA Contact: Lucie Leistnerova
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-09 08:31 UTC by Irit Goihman
Modified: 2018-01-24 10:40 UTC (History)
3 users (show)

Fixed In Version: vdsm v4.19.45
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-01-24 10:40:53 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-4.1+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 86098 0 ovirt-4.1 MERGED fix examples in the documentation of vdsm-client 2021-02-17 15:48:43 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.