Bug 1478599

Summary: older versions of lvm do not support --reportformat=json
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Alfredo Deza <adeza>
Component: Ceph-VolumeAssignee: Alfredo Deza <adeza>
Status: CLOSED ERRATA QA Contact: shylesh <shmohan>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0CC: anharris, aschoen, ceph-eng-bugs, ceph-qe-bugs, gmeno, hnallurv, kdreyer
Target Milestone: rc   
Target Release: 3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: RHEL: ceph-12.2.0-1.el7cp Ubuntu: ceph_12.2.0-2redhat1xenial Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-05 23:39:05 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 Alfredo Deza 2017-08-04 23:02:02 UTC
Description of problem: Older versions of lvm do not allow --reportformat flags which the ceph-volume lvm api uses.


How reproducible: On systems with older lvm versions like Xenial


Steps to Reproduce: Run `ceph-volume lvm prepare` in Xenial

Actual results:
> sudo vgs --reportformat=json
> vgs: unrecognized option '--reportformat=json'


Additional info: The use of JSON needs to be dropped, and parsing of the CLI output needs to be implemented in ceph_volume/devices/lvm/api.py

lvm allows filtering, ordering, and separator addition(s) so it is a matter of defining this correctly and then parsing the output.

Comment 2 Alfredo Deza 2017-08-21 20:53:53 UTC
Verified working on Xenial.

merged commit 60eb0e5 into master

Comment 3 Ken Dreyer (Red Hat) 2017-08-21 21:20:03 UTC
Would you please do the cherry-pick to luminous so it'll be in v12.2.0?

Comment 10 errata-xmlrpc 2017-12-05 23:39:05 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-2017:3387