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.
Bug 2176778 - Update vdo support tools help messages to reflect VDO integration to LVM
Summary: Update vdo support tools help messages to reflect VDO integration to LVM
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: vdo
Version: 9.3
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: rc
: ---
Assignee: sclafani
QA Contact: Filip Suba
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-09 09:45 UTC by Filip Suba
Modified: 2023-11-07 10:10 UTC (History)
3 users (show)

Fixed In Version: vdo-8.2.2.2-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-11-07 08:37:57 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-151197 0 None None None 2023-03-09 09:47:01 UTC
Red Hat Product Errata RHBA-2023:6586 0 None None None 2023-11-07 08:38:00 UTC

Description Filip Suba 2023-03-09 09:45:18 UTC
Description of problem:
After change to LVM it might be harder for a user to determine "<vdoBacking>" or "<device>". Help pages of vdo support tools should be updated with an explanation of what to use as a <device> when using LVM to create a VDO volume.

Version-Release number of selected component (if applicable):
vdo-8.2.0.2-1.el9
vdo-support-8.2.0.2-1.el9

How reproducible:
100%

Steps to Reproduce:
1. vdodumpconfig --help
2.
3.

Actual results:
vdodumpconfig - dump the configuration of a VDO volume from its backing
                store.

SYNOPSIS
  vdodumpconfig <vdoBacking>

DESCRIPTION
  vdodumpconfig dumps the configuration of a VDO volume, whether or not
  the VDO is running.
OPTIONS
    --help
       Print this help message and exit.

    --version
       Show the version of vdodmeventd.

Expected results:
Add an example of how to use it with LVMVDO (vdodumpconfig /dev/mapper/vg-vpool0_vdata) and add an explanation that vdodumpconfig should be used with /dev/mapper/*VG-VPOOL*_vdata. 


Additional info:

Comment 6 Filip Suba 2023-07-17 17:48:25 UTC
Verified with vdo-8.2.2.2-1.el9.

Comment 8 errata-xmlrpc 2023-11-07 08:37:57 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 (vdo and kmod-kvdo bug fix and enhancement update), 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-2023:6586


Note You need to log in before you can comment on or make changes to this bug.