Bug 1658565

Summary: yum in podman container fails with: Cannot rename directory
Product: Red Hat Enterprise Linux 8 Reporter: Christian Heimes <cheimes>
Component: yumAssignee: Jaroslav Rohel <jrohel>
Status: VERIFIED --- QA Contact: Radek Bíba <rbiba>
Severity: unspecified Docs Contact:
Priority: low    
Version: 8.0CC: amatej, cheimes, james.antill, vhutsky, vrothber
Target Milestone: rcKeywords: Triaged
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: libdnf-0.35.5-1.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Comment 5 Jaroslav Rohel 2019-09-17 10:51:32 UTC
The problem with moving directory in podman (fuse-overlayfs) was catched in microdnf too: https://bugzilla.redhat.com/show_bug.cgi?id=1700341 .

I implemented a "copy+delete fallback " in the libdnf. And also made some workaround in the librepo.
PR https://github.com/rpm-software-management/libdnf/pull/787
PR https://github.com/rpm-software-management/libdnf/pull/789
PR https://github.com/rpm-software-management/librepo/pull/166

The new libdnf code is used by DNF too. So, the "cross-device link" problem is fixed.

But I see other message "Directory not empty" instead of "Invalid cross-device link" in this bug. Another anomaly of overlayfs? I do not know, but "copy+delete fallback" will be used in this case too. So, I hope that this bug is fixed too.