Bug #34631
Updated by Ian Ballou about 3 years ago
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=2064410 *Description of problem:* After the Pulp 2 to Pulp 3 migration, upstream users have been reporting failing syncs that seem to be related to incorrect permissions in Pulp's artifacts directory. Thread: https://community.theforeman.org/t/katello-4-3-repo-sync-error-errno1-operation-not-permitted/27262/11 From the report, it seems that something changed in Pulp 3 between Pulpcore 3.14 and 3.16 that suddenly made the incorrect permissions cause sync errors. Users have no issues syncing on Katello with Pulpcore 3.14. I'm setting this on the Installer component for now because the installer keeps track of other Pulp-related permissions: https://github.com/theforeman/puppet-pulpcore/blob/master/manifests/config.pp Foreman Maintain is another place where these permissions could be fixed if there is some reason with doing so in the Foreman Installer. *Version-Release number of selected component (if applicable):* Katello 4.3 Satellite 7.0 (Katello 4.3) *How reproducible:* The permissions being wrong is likely 100% reproducible. The repository sync error is unknown right now because the reporting user could sync some repositories. *Steps to Reproduce:* From Grant's comment, to reproduce you would only need to run the switchover upgrade to Pulp 3 6.10 where the Pulp 3 files are on the same volume as the Pulp 2 ones: https://community.theforeman.org/t/katello-4-3-repo-sync-error-errno1-operation-not-permitted/27262/14 *Actual results:* Syncing fails and some files under /var/lib/pulp/media are owned by apache rather than pulp. *Expected results:* Syncing works fine and the files under /var/lib/pulp/media are owned by the pulp user. *Additional info:*