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 2005001 - vdoimport "Command failed. Volume group not found" errors during create [rhel-8.6.0]
Summary: vdoimport "Command failed. Volume group not found" errors during create [rhe...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: lvm2
Version: 8.5
Hardware: x86_64
OS: Linux
urgent
low
Target Milestone: rc
: ---
Assignee: Zdenek Kabelac
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1986885
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)
9 users (show)

Fixed In Version: lvm2-2.03.14-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1986885
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-5154 0 None None None 2022-01-12 23:01:49 UTC
Red Hat Issue Tracker CLUSTERQE-5502 0 None None None 2022-03-15 20:26:40 UTC
Red Hat Issue Tracker RHELPLAN-97549 0 None None None 2021-09-18 10:19:47 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:33:15 UTC 
Fixed upstream  2.03.14.
Comment 3 Corey Marthaler 2021-11-03 03:22:59 UTC 
Marking Verified:Tested in the latest rpms.

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
lvm2-dbusd-2.03.14-1.el8    BUILT: Wed Oct 20 10:18:48 CDT 2021


[root@hayes-02 ~]# vdo create --force --name lvm_import_vdo_sanity --vdoLogicalSize 500G --device /dev/sdd1
Creating VDO lvm_import_vdo_sanity
      The VDO volume can address 928 GB in 464 data slabs, each 2 GB.
      It can grow to address at most 16 TB of physical storage in 8192 slabs.
      If a larger maximum size might be needed, use bigger slabs.
Starting VDO lvm_import_vdo_sanity
Starting compression on VDO lvm_import_vdo_sanity
VDO instance 150 volume is ready at /dev/mapper/lvm_import_vdo_sanity

[root@hayes-02 ~]# lvm_import_vdo --yes --name newVG/newLV /dev/sdd1
Stopping VDO lvm_import_vdo_sanity
Converting VDO lvm_import_vdo_sanity
      Opening /dev/disk/by-id/scsi-36d094660650d1e0022bd29f31e631f3e-part1 exclusively
      Loading the VDO superblock and volume geometry
      Checking the VDO state
      Converting the UDS index
      Converting the VDO
      Conversion completed for '/dev/disk/by-id/scsi-36d094660650d1e0022bd29f31e631f3e-part1': VDO is now offset by 2097152 bytes
  Physical volume "/dev/sdd1" successfully created.
  Volume group "newVG" successfully created
  WARNING: Logical volume newVG/newLV_vpool not zeroed.
  Logical volume "newLV_vpool" created.
  WARNING: Converting logical volume newVG/newLV_vpool to VDO pool volume WITHOUT formating.
  WARNING: Using invalid VDO pool data MAY DESTROY YOUR DATA!
  Logical volume "newLV" created.
  Converted newVG/newLV_vpool to VDO pool volume and created virtual newVG/newLV VDO volume.



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
vdo create --force --name lvm_import_vdo_sanity --vdoLogicalSize 500G --device /dev/sdd1
Creating VDO lvm_import_vdo_sanity
      The VDO volume can address 928 GB in 464 data slabs, each 2 GB.
      It can grow to address at most 16 TB of physical storage in 8192 slabs.
      If a larger maximum size might be needed, use bigger slabs.
Starting VDO lvm_import_vdo_sanity
Starting compression on VDO lvm_import_vdo_sanity
VDO instance 148 volume is ready at /dev/mapper/lvm_import_vdo_sanity

lvm_import_vdo --yes --name newVG/newLV /dev/sdd1
lvs -a -o +devices newVG/newLV
  LV    VG    Attr       LSize   Pool        Origin Data%  Meta%  Move Log Cpy%Sync Convert Devices       
  newLV newVG vwi-a-v--- 500.00g newLV_vpool        0.00                                    newLV_vpool(0)
lvremove -f newVG
  Logical volume "newLV" successfully removed.
vgremove -f newVG
  Volume group "newVG" successfully removed
pvremove /dev/sdd1
  Labels on physical volume "/dev/sdd1" successfully wiped.
lvmdevices -y --deldev /dev/sdd1
Comment 7 Corey Marthaler 2021-11-16 18:07:33 UTC 
Marking Verified in the latest rpms.

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


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 
vdo create --force --name lvm_import_vdo_sanity --vdoLogicalSize 500G --device /dev/sdd1
Creating VDO lvm_import_vdo_sanity
      The VDO volume can address 1 TB in 929 data slabs, each 2 GB.
      It can grow to address at most 16 TB of physical storage in 8192 slabs.
      If a larger maximum size might be needed, use bigger slabs.
Starting VDO lvm_import_vdo_sanity
Starting compression on VDO lvm_import_vdo_sanity
VDO instance 0 volume is ready at /dev/mapper/lvm_import_vdo_sanity

lvm_import_vdo --yes --name newVG/newLV /dev/sdd1
lvs -a -o +devices newVG/newLV
  LV    VG    Attr       LSize   Pool        Origin Data%  Meta%  Move Log Cpy%Sync Convert Devices       
  newLV newVG vwi-a-v--- 500.00g newLV_vpool        0.00                                    newLV_vpool(0)
lvremove -f newVG
  Logical volume "newLV" successfully removed.
vgremove -f newVG
  Volume group "newVG" successfully removed
pvremove /dev/sdd1
  Labels on physical volume "/dev/sdd1" successfully wiped.
lvmdevices -y --deldev /dev/sdd1
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.