Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
In RHEL 8's multipath, a new option was introduced, 'alias_prefix', which allows to set the user_friendly_names prefix, by default "mpath".
While playing with the new options for multipath, I found out that it was allowed to set up a multipath device that has the same name of an existing LV.
If you do this, and you try to reload or restart multipath, nothing happens other than complains from dmsetup because it cannot create the table, as expected.
The problem comes if you add the prefix, rebuild the initramfs image with dracut, and then reboot - then you go into maintenance mode, and the only way to recover that I've found so far is to select the rescue initrd image in grub, or to copy and old image that doesn't contain multipathd (i.e. that wasn't created with "--add multipath".
Version-Release number of selected component (if applicable):
device-mapper-multipath-0.7.8-3.el8.
How reproducible:
Always
Steps to Reproduce:
1. Create a LV called /dev/test/testa
2. Set up 'alias_prefix' to be 'test-test'
3. Run 'multipath -v2 -ll'
4. At this point, multipath will fail to create the map (as expected) since there is already a table 'test-testa'.
5. Recreate initrd via dracut with "--add multipath"
6. Reboot
Actual results:
System will go into maintenance mode
Expected results:
System will boot normally.
Additional info:
I'm attaching to this bz a rdsosreport.txt from the rescue environment. My next test will be booting with more debug and see if I capture more information.
To be honest I'm not sure if this is a multipath problem or a dracut problem. From multipath point of view we do prevent the map to exist, and if we never update dracut to include multipath, there is no issue at all.
Comment 4RHEL Program Management
2021-02-01 07:32:05 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.