Bug 2176778

Summary: Update vdo support tools help messages to reflect VDO integration to LVM
Product: Red Hat Enterprise Linux 9 Reporter: Filip Suba <fsuba>
Component: vdoAssignee: sclafani
Status: CLOSED ERRATA QA Contact: Filip Suba <fsuba>
Severity: low Docs Contact:
Priority: medium    
Version: 9.3CC: awalsh, cwei, slegendr
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: vdo-8.2.2.2-1.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-11-07 08:37:57 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 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