Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
Bug 2125444 - Syncable exports across partitions causes ' Invalid cross-device link' error
Summary: Syncable exports across partitions causes ' Invalid cross-device link' error
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Pulp
Version: 6.11.2
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: 6.13.0
Assignee: satellite6-bugs
QA Contact: Vladimír Sedmík
URL:
Whiteboard:
: 2185931 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-09 04:11 UTC by Partha Aji
Modified: 2023-05-03 13:21 UTC (History)
6 users (show)

Fixed In Version: pulpcore-3.21.1-1, pulpcore-3.18.11-1, pulpcore-3.16.15-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2150125 (view as bug list)
Environment:
Last Closed: 2023-05-03 13:21:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github pulp pulpcore issues 3187 0 None closed FS Exporter should copy if it can't hard link 2022-10-19 00:09:51 UTC
Red Hat Issue Tracker SAT-14438 0 None None None 2022-12-12 21:05:20 UTC
Red Hat Product Errata RHSA-2023:2097 0 None None None 2023-05-03 13:21:59 UTC

Description Partha Aji 2022-09-09 04:11:56 UTC 
Description of problem:
If the export destination is in a different partition than `/var/lib/pulp/media` then syncable exports raises an eroor along the lines of 
` Invalid cross-device link `/var/lib/pulp/media/artifact/7a/831f9f90bf4d21027572cb503d20b702de8e8785b02c0397445c2e481d81b3' -> '/exports/repo/Packages/b/bear-4.1-1.noarch.rpm'`

Version-Release number of selected component (if applicable):
Sat 6.11.2

How reproducible:
Always

Steps to Reproduce:
1. Administer -> Settings -> Content -> Set 'Pulp 3 export destination filepath' to a path that is in a different partition from /var/lib/pulp/exports
2. Add the partition path to `ALLOWED_EXPORT_PATHS` in  `/etc/pulp/settings.py` and restart services
3. Make sure pulp user has write access to that path
4. Sync a custom repo in your satellite
5. `hammer content-export complete repository --id=<repo id> --format=syncable` 

Actual results:
Error along


```
Error: [Errno 18] Invalid cross-device link: 

/var/lib/pulp/media/artifact/7a/831f9f90bf4d21027572cb503d20b702de8e8785b02c0397445c2e481d81b3' -> '/exports/Default_Organization/cv/2.0/2022-09-09T02-42-15-00-00/custom/custom/repo/Packages/b/bear-4.1-1.noarch.rpm'
```
Expected results:

It should be writing to a new partition instead of trying to symlink.

Additional info:
Comment 1 Daniel Alley 2022-09-23 18:17:52 UTC 
https://github.com/pulp/pulpcore/pull/3188/
Comment 4 Joniel Pasqualetto 2023-04-11 16:09:18 UTC 
*** Bug 2185931 has been marked as a duplicate of this bug. ***
Comment 7 errata-xmlrpc 2023-05-03 13:21:46 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 (Important: Satellite 6.13 Release), 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/RHSA-2023:2097
Note You need to log in before you can comment on or make changes to this bug.