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 2004999 - [RFE] Create a tool to convert native VDO volumes to LVM-managed VDO volumes [rhel-8.6.0]
Summary: [RFE] Create a tool to convert native VDO volumes to LVM-managed VDO volumes ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: lvm2
Version: 8.0
Hardware: Unspecified
OS: Unspecified
urgent
unspecified
Target Milestone: rc
: ---
Assignee: Zdenek Kabelac
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1930261
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-16 14:31 UTC by RHEL Program Management Team
Modified: 2022-05-10 16:37 UTC (History)
10 users (show)

Fixed In Version: lvm2-2.03.14-1.el8
Doc Type: Enhancement
Doc Text:
Clone Of: 1930261
Environment:
Last Closed: 2022-05-10 15:21:57 UTC
Type: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CLUSTERQE-5153 0 None None None 2022-01-12 22:01:50 UTC
Red Hat Issue Tracker CLUSTERQE-5501 0 None None None 2022-03-15 20:26:45 UTC
Red Hat Issue Tracker RHELPLAN-97547 0 None None None 2021-09-18 10:19:32 UTC
Red Hat Product Errata RHBA-2022:2038 0 None None None 2022-05-10 15:22:23 UTC

Comment 1 Zdenek Kabelac 2021-09-22 14:36:18 UTC 
Fixed upstream 2.03.14
Comment 3 Corey Marthaler 2021-11-09 15:40:56 UTC 
Marking Verified:Tested based on the completion of the following regression scenarios.

kernel-4.18.0-348.4.el8.kpq0    BUILT: Wed Oct 27 15:00:32 CDT 2021
lvm2-2.03.14-1.el8    BUILT: Wed Oct 20 10:18:17 CDT 2021
lvm2-libs-2.03.14-1.el8    BUILT: Wed Oct 20 10:18:17 CDT 2021
vdo-6.2.5.74-14.el8    BUILT: Fri Aug 20 17:56:40 CDT 2021
kmod-kvdo-6.2.5.72-81.8_6.el8    BUILT: Tue Oct 12 10:43:50 CDT 2021


SCENARIO - [attempt_non_existence_device_conversion]
Test the conversion attempt of a non existent device

SCENARIO - [attempt_existent_non_vdo_device_conversion]
Test the conversion attempt of an existent but non vdo device

SCENARIO - [basic_vdo_create_and_convert_to_lvm]
Test the basic conversion of an existent vdo volume to lvm2 using the device name

SCENARIO - [basic_already_stopped_vdo_create_and_convert_to_lvm]
Test the basic conversion of an existent, but stopped vdo volume to lvm2 using the device name

SCENARIO - [xfs_io_vdo_create_and_convert_to_lvm]
Test the data populated conversion of an xfs + vdo volume to lvm

SCENARIO - [ext3_io_vdo_create_and_convert_to_lvm]
Test the data populated conversion of an ext3 + vdo volume to lvm

SCENARIO - [ext4_io_vdo_create_and_convert_to_lvm]
Test the basic conversion of an existent vdo volume to lvm2 using the device name

SCENARIO - [gfs2_io_vdo_create_and_convert_to_lvm]
Test the data populated conversion of an gfs2 + vdo volume to lvm

SCENARIO - [vdo_create_and_convert_to_lvm_full_vdoconf_path]
Test the conversion of an existent vdo volume to lvm2 using the full device path listed in vdoconf.yml

SCENARIO - [vdo_convert_to_lvm_with_given_vg_and_lv_name]
Test the conversion of an existent vdo volume to lvm using a specified (non default) vg and lv name

SCENARIO - [attempt_no_flag_answer_to_lvm_import_vdo_convert]
Test the proceedure for answering no to the lvm_import_vdo conversion question midway through the process (1988504)

SCENARIO - [multiple_vdo_create_and_convert_with_named_vg_operations]
Test the conversion of an existent vdo volume to lvm2 while supplying a vg name to use

SCENARIO - [attempt_in_use_vdovg_name_lvm_import_vdo_convert]
Test the proceedure for converting a second vdo volume when the default name is already in use (1986915)

SCENARIO - [attempt_in_use_lv_name_lvm_import_vdo_convert]
Test the proceedure for converting a vdo volume when the default lv names are already in use (1986915)

SCENARIO - [multi_device_lvm_raid_lvm_import_vdo_convert_default_name]
Test the conversion of a vdo stack on a multi device lvm raid volume (1987024)

SCENARIO - [lvm_linear_lvm_import_vdo_convert_non_default_name]
Test the conversion of a non default name vdo stack on a multi device lvm linear volume

SCENARIO - [vdo_convert_dry_run]
Test the various dry-run conversion options of an existent vdo volume to lvm (bug 1989650)

SCENARIO - [vdo_convert_dry_run_failure_attempts]
Test the various dry-run conversion options in given invalid devices

SCENARIO - [multi_device_md_raid_lvm_import_vdo_convert]
Test the conversion of a vdo stack on a multi device md raid volume

SCENARIO - [crypt_device_lvm_import_vdo_convert]
Test the conversion of a vdo stack on a luks volume

SCENARIO - [large_vdo_logical_size_convert_to_lvm]
Test the basic conversion of a large (4t) logical sized existent vdo volume to lvm (1996227)

SCENARIO - [small_vdo_logical_size_convert_to_lvm]
Test the basic conversion of a small (3k, 8k, 10k) logical sized existent vdo volume to lvm (1996227|2005006)

SCENARIO - [in_use_vdo_conversion_attempt]
Attempt to convert an in-use mounted vdo volume to lvm (bug 2005449)
Comment 7 Corey Marthaler 2021-12-01 19:44:31 UTC 
Marking verified based on the completion of the above regression scenarios on the latest kernel.

kernel-4.18.0-353.el8    BUILT: Thu Nov 25 15:02:09 CST 2021
lvm2-2.03.14-1.el8    BUILT: Wed Oct 20 10:18:17 CDT 2021
lvm2-libs-2.03.14-1.el8    BUILT: Wed Oct 20 10:18:17 CDT 2021
Comment 9 errata-xmlrpc 2022-05-10 15:21: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 (lvm2 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-2022:2038
Note You need to log in before you can comment on or make changes to this bug.