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.

Description of problem:

The name given to "vdo create --device" needs to be stable across reboots.  I think that is ultimately impossible, and VDO should somehow cope without writing that name to its config file.  Better yet, the config file could be removed completely by writing all its information to the backing device itself, no?

LVM2 works like this, for example.  It can assemble a volume group purely from information stored on the physical volumes themselves.

Version-Release number of selected component (if applicable):
6.1.1.8

How reproducible:
Always

Steps to Reproduce:
# vdo create --name vdo0 --device /dev/vgroup0/lvol0
# lvrename vgroup lvol0 lvol1
(/dev/mapper/vdo0 keeps working)
# vdo stop --name vdo0
# vdo start --name vdo0
Starting VDO vdo0
vdo: ERROR - Could not set up device mapper for vdo0
vdo: ERROR - vdodumpconfig: Failed to make FileLayer from '/dev/vgroup0/lvol0' with No such file or directory

Actual results:
As above

Expected results:
"vdo start --name vdo0" succeeds.

This sounds similar to BZ 1540619, except that instead of a physical device name changing (e.g.: /dev/sdc to /dev/sdd), it's an LVM logical volume changing its name.

I believe this BZ is aking to fix exactly the same as BZ 1540619 - a way to identify the underlying device persistently. Yet this one gives a good and easy reproducer for the issue using LVM.

*** This bug has been marked as a duplicate of bug 1540619 ***