Actions
Issue #1463
closedNode sync fails with "RuntimeError: Will not create a symlink to a non-existent source"
Start date:
Due date:
Estimated time:
Severity:
3. High
Version:
2.6.5
Platform Release:
2.8.0
OS:
RHEL 6
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:
Description
This seems to be the cause of the following BZ's:
https://bugzilla.redhat.com/show_bug.cgi?id=1285830
https://bugzilla.redhat.com/show_bug.cgi?id=1288855
https://bugzilla.redhat.com/show_bug.cgi?id=1276911
There is a workaround; however, in at least some one case led to the data being different on the parent and child nodes.
https://access.redhat.com/solutions/2069243
The error
RuntimeError: Will not create a symlink to a non-existent source"
seems to occur because the database record of the unit is transferred but the corresponding file is not.
This has only been seen with units of type YumMetadataFile
Files
Actions
Better support updated units with associated files. closes #1463.