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:
podman run with --rm will report "device or resource busy" with NFS storage. The same error will also be report when try to remove a running container with -f. They should be similar problem.
Version-Release number of selected component (if applicable):
podman-3.4.3-0.7.el9.x86_64
How reproducible:
100%
Steps to Reproduce:
1. mount NFS to /var/lib/containers/storage to let podman use NFS storage
2. RUN a container with --rm or start a container then try to remove it with -f
# podman run --rm quay.io/libpod/busybox sleep 2
or
# podman run -d quay.io/libpod/busybox sleep 99
# podman rm -f $cid
Actual results:
Error message is raise by the command line, and the command finished with status 125.
ERRO[0002] Error removing container 5d4d1f0166c5d08db7b1f95b7185214aa0c4324b2848cc346e57badea593d9de: error removing container 5d4d1f0166c5d08db7b1f95b7185214aa0c4324b2848cc346e57badea593d9de root filesystem: 2 errors occurred:
* unlinkat /var/lib/containers/storage/overlay-containers/5d4d1f0166c5d08db7b1f95b7185214aa0c4324b2848cc346e57badea593d9de/userdata/.nfs0000000006138ca5000003b1: device or resource busy
* unlinkat /var/lib/containers/storage/overlay-containers/5d4d1f0166c5d08db7b1f95b7185214aa0c4324b2848cc346e57badea593d9de/userdata/.nfs0000000006138ca5000003b1: device or resource busy
Expected results:
container can be delete without the error message
Additional info:
We can remove a stopped container successfully. And if we checked the container status with podman ps -a after the command finished. We can see that the container is actually removed.