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.
Bug 1393506 - Puppet4: /etc/puppetlabs/puppet/node.rb requires to be labeled with foreman_enc_t
Summary: Puppet4: /etc/puppetlabs/puppet/node.rb requires to be labeled with foreman_e...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: SELinux
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: Lukas Zapletal
QA Contact: Lukas Pramuk
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-09 17:32 UTC by Lukas Pramuk
Modified: 2019-09-26 14:48 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:49:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 17460 0 None None None 2016-11-23 12:05:51 UTC

Description Lukas Pramuk 2016-11-09 17:32:43 UTC
Description of problem:
/etc/puppetlabs/puppet/node.rb requires to be labeled with foreman_enc_t
(the same as is /etc/puppet/node.rb)

Puppet3 labels:
# bzcat /etc/selinux/targeted/active/modules/400/foreman/cil | grep /etc/puppet
(filecon "/etc/puppet/node.rb" any (system_u object_r foreman_enc_t ((s0) (s0))))

Puppet4 node.rb:
# ll -Z `find /etc/puppetlabs/ -name node.rb`
-r-xr-x---. puppet puppet system_u:object_r:puppet_etc_t:s0 /etc/puppetlabs/puppet/node.rb


Version-Release number of selected component (if applicable):
@satellite-6.3.0-6.1.beta.el7sat.noarch
foreman-selinux-1.13.1-1.el7.noarch


Steps to Reproduce:
ll -Z /etc/puppetlabs/puppet/node.rb

Actual results:
puppet_etc_t

Expected results:
foreman_enc_t

Comment 1 Lukas Pramuk 2016-11-09 17:42:11 UTC
Workaround:

# semanage fcontext -a -t foreman_enc_t '/etc(/puppetlabs)?/puppet/node.rb'

Comment 3 Lukas Zapletal 2016-11-23 11:31:31 UTC
Thanks, fixed!

Comment 4 Bryan Kearney 2016-11-25 15:15:34 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/17460 has been resolved.

Comment 5 Lukas Pramuk 2017-08-10 20:26:24 UTC
VERIFIED.

@satellite-6.3.0-16.0.beta.el7sat.noarch
puppetserver-2.7.2-2.el7sat.noarch
puppet-agent-1.8.2-2.el7sat.x86_64
foreman-selinux-1.15.2-1.el7sat.noarch

by simple reproducer on both upgraded and fresh p4 install:

# ll -Z /etc/puppetlabs/puppet/node.rb 
-r-xr-x---. puppet puppet system_u:object_r:foreman_enc_t:s0 /etc/puppetlabs/puppet/node.rb

>>> puppet4 enc has the correct selinux label (foreman_enc_t)

Comment 6 Satellite Program 2018-02-21 16:49:54 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.

For information on the advisory, and where to find the updated files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:0336


Note You need to log in before you can comment on or make changes to this bug.