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.
+++ This bug was initially created as a clone of Bug #2087734 +++
Description of problem:
Image build tools that use the DNF Python API directly have issues completing successfully right now because the Base object leaks page file descriptors, which locks up all the mounts and prevents successful filesystem unmounting to save the final disk.
This was fixed upstream as https://github.com/rpm-software-management/dnf/commit/5ce5ed1ea08ad6e198c1c1642c4d9ea2db6eab86
Please backport this so that this problem is fixed.
Version-Release number of selected component (if applicable):
4.10.0-5.el9_0
Additional info:
This was reported to livecd-tools here: https://github.com/livecd-tools/livecd-tools/issues/232
Comment 1Richard W.M. Jones
2022-05-18 16:08:31 UTC
I can do dev work here, but someone on the packaging team will need to do QE.
Obviously dnf is quite an important package so we can't leave it to chance.
Very low risk of regressions as far as we know.
Comment 3Richard W.M. Jones
2022-05-23 13:12:42 UTC
Yeah that'll be fine. It's more important that we don't break dnf than
that we prove that livecd-tools is fixed :-)
Comment 4Richard W.M. Jones
2022-05-23 17:42:05 UTC
The baseos-ci.brew-build.ci-dnf-stack-gating.functional test failed with:
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: Test plugins-core/modulesync.feature
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: [ 17:09:42 ] :: [ FAIL ] :: Command './container-test run --container-arg='--security-opt' --container-arg='seccomp=unconfined' plugins-core/modulesync.feature' (Expected 0, got 1)
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: Duration: 3s
:: Assertions: 0 good, 1 bad
:: RESULT: FAIL (Test plugins-core/modulesync.feature)
whatever that means. I can't believe it would be caused by this change.
Also I don't know where these tests are located.
Comment 6Richard W.M. Jones
2022-05-24 09:47:01 UTC
I ran the test 3 times and it failed each time. It did not fail
on the previous build of this package in RHEL 9. I don't have a
theory as to why this particular patch could cause a failure in
this particular test. (The failure might also be caused by environment
changes, so this patch might not be the cause.)
Needs someone who is more familiar with the tests to look at this.
At the moment I don't want to waive this test, given such an important
RHEL package.
Comment 7Richard W.M. Jones
2022-05-24 09:47:36 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 (dnf bug fix and enhancement update), 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-2022:8297