Problem: I’m unable to Sync Ubuntu repo in Foreman. Always Sync is Failing.
Error: PLP0000: [Errno 2] No such file or directory: u'/var/cache/pulp/reserved_resource_worker-4@sesklsw01.astrazeneca.net/
Expected outcome: Sync should be successful
Foreman and Proxy versions: 1.22
Foreman and Proxy plugin versions: 1.22
Other relevant data:
[e.g. logs from Foreman and/or the Proxy, modified templates, commands issued, etc]
(for logs, surround with three back-ticks to get proper formatting, e.g.)
PLP0000: [Errno 2] No such file or directory: u'/var/cache/pulp/reserved_resource_worker-4@sesklsw01.astrazeneca.net/58080e94-3409-41d4-b142-95cf4b8ac05a/packages/14/09/gtk-sharp3-gapi_2.99.3-2_amd64.deb'
Repo Configuration:
This error generally indicates that the package in question did not download successfully.
Unfortunately there are many possible causes for an unsuccessful download.
If this always happens on the exact same package, then it is possible there is something wrong with the mirror you are using, so one thing to try is to use another mirror.
One thing you could try (at least for debugging purposes), is to limit your repository to individual components and see if those work. In your image above the Components field is empty, which means pulp deb will try to download all components. In the case of Ubuntu that is “main,multiverse,restricted,universe”.
You could try syncing only “Components: main,multiverse,restricted” for now. (As far as I can tell the package that is throwing the error in your example is from universe which is also one of the largest components.)
I will keep looking and post again if I find anything.
So i verified the following: The package file that caused the error in your log (“gtk-sharp3-gapi_2.99.3-2_amd64.deb”) is described in the following file on your mirror:
I was able to manually download this file and verify its sha256sum (54688ecffce2663bf30d4ebaf40ce822d157f32d2ba9c28203bb4b52b7986684) against the one provided in the Packages.gz file, so there is nothing obviously wrong with your mirror.
You could try to do the same on your actual foreman server to see if there is some weird networking effect at your location. (I have seen some strange things in my time).
All of the above only makes sense if you are always getting the above error on the exact same package. If you are getting similar errors with different packages for each attempted sync, then your problem is probably something else…
I am encountering an issue related to the package mentioned from above.
Katello reports:
Error: DEBSYNC002: Unable to sync 42c8dc77-de30-4a45-b41f-885d0f18e3cb from http://us.archive.ubuntu.com/ubuntu: mismatching checksums for gtk-sharp3-gapi_2.99.3-2_amd64.deb: expected 7fa46525dc131ce5f84e163d46290b96c42c11a6, actual bd321796011b9c6cf170e9a0267704fac4c814bf
