Jira (PUP-7375) Puppet does not change file to directory when selinux is enabled

[Melissa Stone (JIRA)]

Title: Message Title

Melissa Stone commented on PUP-7375   Re: Puppet does not change file to directory when selinux is enabled I was able to reproduce this with puppet-agent 5.5.3.260.ge0ad970 and the included ruby 2.4.4 [root@bi040qter7lkjw5 ~]# selinuxenabled ; echo $? 0 [root@bi040qter7lkjw5 ~]# sestatus SELinux status: enabled SELinuxfs mount: /sys/fs/selinux SELinux root directory: /etc/selinux Loaded policy name: targeted Current mode: enforcing Mode from config file: enforcing Policy MLS status: enabled Policy deny_unknown status: allowed Max kernel policy version: 31 [root@bi040qter7lkjw5 ~]# cat /etc/sysconfig/selinux   # This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing - SELinux security policy is enforced. # permissive - SELinux prints warnings instead of enforcing. # disabled - No SELinux policy is loaded. SELINUX=enforcing # SELINUXTYPE= can take one of three two values: # targeted - Targeted processes are protected, # minimum - Modification of targeted policy. Only selected processes are protected. # mls - Multi Level Security protection. SELINUXTYPE=targeted     [root@bi040qter7lkjw5 ~]# puppet --version 6.0.0 [root@bi040qter7lkjw5 ~]# /opt/puppetlabs/puppet/bin/ruby --version ruby 2.4.4p296 (2018-03-28 revision 63013) [x86_64-linux] [root@bi040qter7lkjw5 ~]# stat /tmp/foo File: ‘/tmp/foo’ Size: 0 Blocks: 0 IO Block: 4096 regular empty file Device: fd00h/64768d Inode: 101596055 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root) Context: unconfined_u:object_r:user_tmp_t:s0 Access: 2018-06-20 16:49:24.252725530 +0000 Modify: 2018-06-20 16:49:24.252725530 +0000 Change: 2018-06-20 16:49:24.252725530 +0000 Birth: - [root@bi040qter7lkjw5 ~]# cat manifest.pp File { owner => 'root', group => 'root', mode => '0644', } file { '/tmp/foo': ensure => directory, } file { '/tmp/foo/bar': ensure => file, } [root@bi040qter7lkjw5 ~]# puppet apply manifest.pp --trace Notice: Compiled catalog for bi040qter7lkjw5.delivery.puppetlabs.net in environment production in 0.02 seconds Error: Not a directory @ rb_file_s_lstat - /tmp/foo/bar /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/file_system/file_impl.rb:144:in `lstat' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/file_system/file_impl.rb:144:in `lstat' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/file_system.rb:317:in `lstat' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/selinux.rb:261:in `file_lstat' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/selinux.rb:45:in `get_selinux_default_context' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type/file/selcontext.rb:45:in `retrieve_default_context' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type/file/selcontext.rb:103:in `block (2 levels) in <module:Puppet>' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type.rb:835:in `set_default' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type.rb:2508:in `block in set_parameters' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type.rb:2507:in `each' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type.rb:2507:in `set_parameters' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type.rb:2396:in `initialize' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type/file.rb:490:in `initialize' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/resource.rb:461:in `new' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/resource.rb:461:in `to_ral' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:643:in `block in to_catalog' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:635:in `each' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:635:in `to_catalog' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:516:in `to_ral' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/apply.rb:269:in `block in main' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/context.rb:65:in `override' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:251:in `override' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/apply.rb:233:in `main' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/apply.rb:174:in `run_command' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:382:in `block in run' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:666:in `exit_on_fail' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:382:in `run' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:137:in `run' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:73:in `execute' /opt/puppetlabs/puppet/bin/puppet:5:in `<main>' Add Comment   This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.