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:
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.7.0-8.el8

Additional info:
This was reported to livecd-tools here: https://github.com/livecd-tools/livecd-tools/issues/232

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.

Thank you Rich for taking this!

Yeah that'll be fine.  It's more important that we don't break dnf than
that we prove that livecd-tools is fixed :-)

Any chance this is fixed in EL8.7?

I don't know what alternative dnf download you are referring to.

Ok, AlmaLinux 8.7 Beta came out today... so I cherry picked the dnf related packages, added them to a local repo, updated my build host so it had the newer DNF... and bam... it is working now.  Yeah.

So, I guess the answer to my question is... yes... it is fixed in EL8.7.

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:7712