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:
Docker can schedule deferred device removal and can cancel the removal later if need be. That is deferred removal can be cancelled before device is actually removed.
libdevmapper removes the symlink to device node when deferred removal is scheduled. But if removal is cancelled, that symlink never reappears. And that means device is no more accessible.
Opening this bug to take care of deferred device removal cancellation case.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
For now, this is not documented well, but it's actually:
dmsetup message <dm_name> 0 "@cancel_deferred_remove"
Works fine if we use DM_UDEV_DISABLE_LIBRARY_FALLBACK flag for DM cookies (passed in as part of dm_task_set_cookie call).
Still needs better device node handling in case we don't rely on udev fully and we still have the fallback code that checks udev enabled. In this case, we need to put the device node back if previous "deferred remove" operation removed the node already (as part of the libdm fallback code).