1986885 – vdoimport "Command failed. Volume group not found" errors during create

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 1986885 - vdoimport "Command failed. Volume group not found" errors during create

Summary: vdoimport "Command failed. Volume group not found" errors during create

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Red Hat Enterprise Linux 8
Classification:	Red Hat
Component:	lvm2
Sub Component:
Version:	8.5
Hardware:	x86_64
OS:	Linux
Priority:	urgent
Severity:	low
Target Milestone:	beta
Target Release:	---
Assignee:	Zdenek Kabelac
QA Contact:	cluster-qe@redhat.com
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:	1930261 2005001
TreeView+	depends on / blocked

Reported:	2021-07-28 13:41 UTC by Corey Marthaler
Modified:	2023-09-07 06:49 UTC (History)
CC List:	8 users (show)
Fixed In Version:	lvm2-2.03.12-9.el8
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Clones:	2005001 (view as bug list)
Environment:
Last Closed:	2021-11-09 19:45:54 UTC
Type:	Bug
Target Upstream Version:
Embargoed:
Dependent Products:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Issue Tracker	CLUSTERQE-4880	0	None	None	None	2021-09-09 04:03:32 UTC
Red Hat Product Errata	RHBA-2021:4431	0	None	None	None	2021-11-09 19:46:18 UTC

Description Corey Marthaler 2021-07-28 13:41:56 UTC

Description of problem:
This was mentioned in a comment in the feature bug 1930261, but I wanted this tracked separately for QA to remember to verify. There are a few lines that have to do with the VG create that should be hidden from the user, unless there is an actual failure during this convert operation.

Device does not exist.
Command failed.
Volume group "vgD" not found
Cannot process volume group vgD

[root@hayes-03 ~]# vdoimport --name vgD/lvD /dev/disk/by-id/scsi-36d09466083d8e100233c17f0209a73b5-part1
Device does not exist.
Command failed.
Volume group "vgD" not found
Cannot process volume group vgD
Stopping VDO VB
Converting VDO VB
Opening /dev/disk/by-id/scsi-36d09466083d8e100233c17f0209a73b5-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-36d09466083d8e100233c17f0209a73b5-part1': VDO is now offset by 2097152 bytes
Physical volume "/dev/disk/by-id/scsi-36d09466083d8e100233c17f0209a73b5-part1" successfully created.
Volume group "vgD" successfully created
WARNING: Logical volume vgD/lvD_vpool not zeroed.
Logical volume "lvD_vpool" created.
WARNING: Converting logical volume vgD/lvD_vpool to VDO pool volume WITHOUT formating.
WARNING: Using invalid VDO pool data MAY DESTROY YOUR DATA!
Do you really want to convert vgD/lvD_vpool? [y/n]: y
Logical volume "lvD" created.
Converted vgD/lvD_vpool to VDO pool volume and created virtual vgD/lvD VDO volume.

Version-Release number of selected component (if applicable):
kernel-4.18.0-323.el8 BUILT: Wed Jul 14 12:12:22 CDT 2021
lvm2-2.03.12-5.el8 BUILT: Tue Jul 13 11:50:03 CDT 2021
lvm2-libs-2.03.12-5.el8 BUILT: Tue Jul 13 11:50:03 CDT 2021
vdo-6.2.5.65-14.el8 BUILT: Thu Jul 22 12:56:43 CDT 2021
kmod-kvdo-6.2.5.65-79.el8 BUILT: Thu Jul 22 12:59:43 CDT 2021

How reproducible:
Everytime

Comment 1 Zdenek Kabelac 2021-08-31 21:25:59 UTC

Pushed https://listman.redhat.com/archives/lvm-devel/2021-August/msg00044.html to hide messages.

Comment 5 Marian Csontos 2021-09-09 14:17:27 UTC

Scratch build: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=39647501
Repo: http://brew-task-repos.usersys.redhat.com/repos/scratch/mcsontos/lvm2/2.03.12/9.el8/

Comment 6 Corey Marthaler 2021-09-14 17:00:31 UTC

The "Command failed." warnings are fixed in the latest scratch build. Marking Verified:Tested

kernel-4.18.0-340.el8 BUILT: Thu Sep 2 16:16:14 CDT 2021
lvm2-2.03.12-9.el8 BUILT: Tue Sep 14 09:53:56 CDT 2021
lvm2-libs-2.03.12-9.el8 BUILT: Tue Sep 14 09:53:56 CDT 2021

[root@hayes-03 ~]# vdo create --force --name lvm_import_vdo_sanity --vdoLogicalSize 500G --device /dev/sdd1
Creating VDO lvm_import_vdo_sanity
The VDO volume can address 442 GB in 221 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 44 volume is ready at /dev/mapper/lvm_import_vdo_sanity

[root@hayes-03 ~]# 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-36d09466083d8e100233c17f9212bf63e-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-36d09466083d8e100233c17f9212bf63e-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.

Comment 10 Corey Marthaler 2021-09-22 20:28:48 UTC

Marking verified in the latest rpms.

kernel-4.18.0-343.el8    BUILT: Thu Sep 16 18:25:30 CDT 2021
lvm2-2.03.12-10.el8    BUILT: Mon Sep 20 03:30:20 CDT 2021
lvm2-libs-2.03.12-10.el8    BUILT: Mon Sep 20 03:30:20 CDT 2021

[root@hayes-03 ~]# 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-36d09466083d8e100233c17f9212bf63e-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-36d09466083d8e100233c17f9212bf63e-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.

Comment 12 errata-xmlrpc 2021-11-09 19:45:54 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-2021:4431

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