Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionSteven J. Levine
2016-06-13 21:40:08 UTC
This needs to be documented for 7.3:
+++ This bug was initially created as a clone of Bug #1334682 +++
This is bug tracks a set of new and related features introduced in the area of reporting and formatting report output which are closely related to each other:
- bug #1334655 (Enhance reporting code in libdevmapper to support report groups with different output formats)
- bug #1334659 (Make it possible to report output from lvm2 reporting commands in JSON format)
- bug #1334667 (Add new lvm2 command to do complete report per VG)
- bug #1334674 (Issue warnings, errors and status per object from lvm2 command line tools via report)
- bug #1334678 (Make it possible to query lvm2 command status report)
--- Additional comment from Peter Rajnoha on 2016-05-10 06:38:52 EDT ---
Current development code is in dev-prajnoha-json branch (a need for JSON report output triggered all the particular changes mentioned in comment #1):
https://git.fedorahosted.org/cgit/lvm2.git/log/?h=dev-prajnoha-json
--- Additional comment from Peter Rajnoha on 2016-05-10 06:43:37 EDT ---
Future output formats may also include YAML and XML - the changes mentioned in comment #0 are designed to easily include support for various other formats in the future.
--- Additional comment from Peter Rajnoha on 2016-05-10 06:54:32 EDT ---
One more:
- bug #1334692 (Make it possible to switch report output format to dense form)