A symlink issue was introduced with 2.8.0, but it's symptom is observable when serving content and not with sync/publish issues[0].
This looks like a separate issue. Can you file an issue against Pulp and include the specific AVC denials you are encountering? Also showing the symlink link and target POSIX and selinux labels with `ls -laZ` would be helpful. [0]: https://pulp.plan.io/issues/1791 -Brian On 03/30/2016 01:47 PM, Sparks, Alan wrote: > Is there a best way to move the content of /var/lib/pulp to a different > file system? I’ve tried tar’ing the data over, with –“-selinux --acls > –xattrs” switches, and then symlinking /var/lib/pulp to the new > location. Triggers all sorts of selinux issues, even after changing > the type of the symlink I wind up with lots of messages from celery > tasks (like denied search from “/data” and even “/”). > > > > In the end, all my sync/publish tasks end up with a > > Task Failed > > [Errno 13] Permission denied: '/var/lib/pulp/published' > > > > I know that all the published subdirectories have symlinks to the > original locations (under /var/lib/pulp). I can use a bind mount to > solve it, but wondered if there’s a procedure to move the data and > change the configuration to use the new location. > > > > _______________________________________________ > Pulp-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/pulp-list > _______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
