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 1767491 - Unable to 'vdo import' when there are no active device-mapper tables
Summary: Unable to 'vdo import' when there are no active device-mapper tables
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: vdo
Version: 8.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: bjohnsto
QA Contact: Filip Suba
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-31 14:57 UTC by Andy Walsh
Modified: 2021-09-06 15:24 UTC (History)
2 users (show)

Fixed In Version: 6.2.2.26
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-28 16:43:10 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:1782 0 None None None 2020-04-28 16:43:21 UTC

Description Andy Walsh 2019-10-31 14:57:17 UTC 
Description of problem:
Attempting to import a VDO volume into a system with no active device-mapper tables fails with "ERROR - list index out of range".  If there are active device-mapper tables, then the import succeeds.

Version-Release number of selected component (if applicable):
vdo-6.2.2.24-11.el8

How reproducible:
100%

Steps to Reproduce:
1. Make sure there are no active device-mapper tables active by running 'dmsetup table' (you should get a 'No devices found' message)
2. Create a new VDO volume 'vdo create --name vdo0 --device /path/to/storage'
3. Stop that VDO volume 'vdo stop -a'
4. Remove the VDO config 'rm /etc/vdoconf.yml'
5. Attempt to import the volume created in step 2 'vdo import --name vdo_imported --device /path/to/storage'

Actual results:
[root@host-10-0-138-30 ~]# vdo import --name vdo_import --device /dev/loop0
Importing VDO vdo_import
vdo: ERROR - list index out of range

Expected results:
[root@host-10-0-138-30 ~]# vdo import --name vdo_import --device /dev/vg/lv1
Importing VDO vdo_import
Starting VDO vdo_import
Starting compression on VDO vdo_import
VDO instance 2 volume is ready at /dev/mapper/vdo_import


Additional info:
The 'vdo import' command uses 'dmsetup table --target vdo' to verify the requested import.
- If there are no active target-type vdo tables, but there are other active tables (i.e.linear), then the output of 'dmsetup table --target vdo' returns no output.
- If there are no active target-type vdo tables, but there are no other active tables, then the output of 'dmsetup table --target vdo' returns 'No devices found'.

Both of those conditions are also true when leaving out '--target vdo'.  Is this a bug in the dmsetup command?
Comment 3 Filip Suba 2020-03-17 13:59:51 UTC 
Verified with vdo-6.2.2.117-13.el8.

# rm -f /etc/vdoconf.yml

# vdo import --name vdo_imported --device /dev/sda
Importing VDO vdo_imported
Starting VDO vdo_imported
Starting compression on VDO vdo_imported
VDO instance 1 volume is ready at /dev/mapper/vdo_imported
Comment 5 errata-xmlrpc 2020-04-28 16:43:10 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, 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-2020:1782
Note You need to log in before you can comment on or make changes to this bug.