Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
When publishing CV on puppet4 Satellite it fails with
PLP0034: The distributor Default_Organization-Library-RHEL_7_2_Server_x86_64 indicated a failed response when publishing repository Default_Organization-Library-RHEL_7_2_Server_x86_64
In task detail we have Actions::Pulp::Repository::DistributorPublish failed to create destination directory: [Errno 13] Permission denied: '/etc/puppetlabs/code/environments/KT_Default_Organization_Library_RHEL_7_2_Server_x86_64_2/'
It is caused by SELinux. Puppet4 has environments in different location and we have to adjust Selinux policy to cope with it.
Version-Release number of selected component (if applicable):
6.3.0 snap3 (with manually pre-installed puppet4)
How reproducible:
always
Steps to Reproduce:
1. Have satellite running on puppet4
2. Create CV with repos and Publish it.
Actual results:
Selinux policy prevents publish task to succeed
Expected results:
Publish task successfully finishes
Additional info:
workaround is to set selinux perms manually
# semanage fcontext -a -t puppet_etc_t '/etc/puppetlabs(/.*)?'
# restorecon -rv /etc/puppetlabs
Satellite doesnt use puppet-selinux and relies on rhel policy.
And the required selinux policy change was added for RHEL7.3:
# bkrsh semanage fcontext -l | grep puppet_etc_t
/etc/puppet(/.*)? all files system_u:object_r:puppet_etc_t:s0
/etc/puppetlabs(/.*)? all files system_u:object_r:puppet_etc_t:s0 <<< this was added
>>> /etc/puppetlabs/ has set puppet_etc_t type
RHEL6.8 policy will be fixed by BZ #1386181 (cloned)
Or it could be RHEL6.9 policy - it depends on Satellite6.3 GA
Comment 5Daniel Lobato Garcia
2017-04-12 08:22:12 UTC
Tentatively closing as RHEL provides this policy in all Satellite supported versions. Please reopen and set a needinfo on me or lzap if it needs anything else done on our side.