Jira (PUP-6038) Puppet sets GID

[Patrick Thyen (JIRA)]

Patrick Thyen created an issue

Puppet / PUP-6038 Puppet sets GID Issue Type: Bug Assignee: Unassigned Created: 2016/03/10 4:26 AM Priority: Major Reporter: Patrick Thyen file { 'zone_dir' : ensure => 'directory', path => '/tmp/test', mode => 'u=rwx,g=rw,a=r', } When Puppet creates a new directory as mentioned above, puppet sets the Sticky-Bit although it is not set. If the directory exist, Puppet doesn't Workaround is: mode => 'u=rwx,g=rw,a=r-t', Add Comment

This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)

[Patrick Thyen (JIRA)]

Patrick Thyen updated an issue

Puppet / PUP-6038 Puppet sets GID

Change By: Patrick Thyen {code}file { ' zone_dir test_dir ' :

ensure  => 'directory',                 path    => '/tmp/test',                 mode    => 'u=rwx,g=rw,a=r',

}{code}

When Puppet creates a new directory as mentioned above, puppet sets the Sticky-Bit although it is not set. If the directory exist, Puppet doesn't Workaround is:

{code}mode =>  'u=rwx,g=rw,a=r-t',{code}

Add Comment

[Henrik Lindberg (JIRA)]

Henrik Lindberg updated an issue

Puppet / PUP-6038 Puppet sets GID

ping Kylo Ginsberg Change By: Henrik Lindberg Scrum Team: Client Platform

Add Comment

[Kylo Ginsberg (JIRA)]

Kylo Ginsberg commented on PUP-6038

Re: Puppet sets GID Thanks for the bug report Patrick Thyen! Can you add information about what puppet version this was found with and what platform(s) you've observed this on?

Add Comment

[Patrick Thyen (JIRA)]

Patrick Thyen commented on PUP-6038

Re: Puppet sets GID Hey Kylo Ginsberg It was Centos 6.7 and Centos 7 with Puppet 3.8

Add Comment

[Sean McDonald (JIRA)]

Sean McDonald updated an issue

Puppet / PUP-6038 Puppet sets GID

Change By: Sean McDonald Labels: triaged

Add Comment

This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)

[Sean McDonald (JIRA)]

Sean McDonald updated an issue

Puppet / PUP-6038 Puppet sets GID

Change By: Sean McDonald Team: Agent

Add Comment

[Moses Mendoza (JIRA)]

Moses Mendoza commented on PUP-6038

Re: Puppet sets GID Was able to reproduce partially - on Centos 7 with Puppet 4.9.4, using this manifest: file { 'test_dir' :

ensure => 'directory', path => '/tmp/test', mode => 'u=rwx,g=rw,a=r', }

The resulting directory created is as: dr--r--r--. 2 root root 6 May 11 00:28 test

Add Comment

[Reid Wahl (JIRA)]

Reid Wahl commented on PUP-6038

Re: Puppet sets GID Moses Mendoza Is that not the expected behavior? I would think that the all = read permission (rather than all + read) coming at the end would override the user and group permissions set in the first and second positions. It's setting absolute permissions for all users rather than ensuring that the read permission is present (a+r) or ensuring that it's absent (a-r).

Add Comment

This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)

[Reid Wahl (JIRA)]

Reid Wahl commented on PUP-6038

Re: Puppet sets GID As it stands, I'm using Fedora 26 with Puppet 5.3.3 and am not able to reproduce there. Perhaps this was resolved in Puppet 4 or 5?

Add Comment

[Josh Cooper (Jira)]

Josh Cooper commented on PUP-6038

Re: Puppet sets GID chmod results in the directory having permissions 444: [root ~]# rm -rf /tmp/test/ [root ~]# mkdir /tmp/test [root ~]# chmod u=rwx,g=rw,a=r /tmp/test [root ~]# stat -c '%a' /tmp/test 444 puppet (6.19.1) behaves the same: [root ~]# rm -rf /tmp/test/ [root ~]# cat sticky.pp file { '/tmp/test': ensure => 'directory', mode => 'u=rwx,g=rw,a=r', } [root ~]# puppet apply sticky.pp Notice: Compiled catalog for xxx in environment production in 0.01 seconds Notice: /Stage[main]/Main/File[/tmp/test]/ensure: created Notice: Applied catalog in 0.01 seconds [root ~]# stat -c '%a' /tmp/test 444 so I'm going to close this as cannot reproduce

Add Comment

This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)