Jira (PUP-9337) Puppet sets permissions for Puppet files every run

Issue Type:	Bug
Assignee:	Unassigned
Created:	2018/11/30 10:48 AM
Priority:	Normal
Reporter:	Paul Schaffer

Puppet Version: 2018.1.5, 2019.0.1
OS Name/Version: Windows 2012 R2, 2016, 2019

File permissions for Puppet files are being set to the same value every run:

```
Resource Event Changed from Changed to

File[C:\ProgramData/PuppetLabs/puppet/cache/state/package_inventory_enabled]
File: /opt/puppetlabs/puppet/modules/puppet_enterprise/manifests/profile/agent.pp Line: 89
Corrective change
0674
664

File[C:\ProgramData/PuppetLabs/pxp-agent/etc/pxp-agent.conf]
File: /opt/puppetlabs/puppet/modules/puppet_enterprise/manifests/pxp_agent.pp Line: 105
Corrective change
0670
660
```

This seems to target package_inventory_enabled most frequently. Every run the permission is set from 0674 to 0664, which would seem to correspond with documentation requirements (https://puppet.com/docs/puppet/6.0/resources_file_windows.html#how-nix-modes-map-to-windows-permissions):

> The group can’t have higher permissions than the owner. Other users can’t have higher permissions than the owner or group. (That is, 0640 and 0755 are supported, but 0460 is not.)

However the next agent run shows the value has reverted and needs to be set again.

This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)

Paul Schaffer (JIRA)

unread,

Nov 30, 2018, 1:50:03 PM11/30/18

to puppe...@googlegroups.com

Paul Schaffer updated an issue

Puppet /

Change By:	Paul Schaffer

*Puppet Version:* 2018.1.5, 2019.0.1
*OS Name/Version:* Windows 2012 R2, 2016, 2019

File permissions for Puppet files are being set to the same value every run:

```
Resource Event Changed from Changed to

File[C:\ProgramData/PuppetLabs/puppet/cache/state/package_inventory_enabled]
File: /opt/puppetlabs/puppet/modules/puppet_enterprise/manifests/profile/agent.pp Line: 89
Corrective change
0674
664

File[C:\ProgramData/PuppetLabs/pxp-agent/etc/pxp-agent.conf]
File: /opt/puppetlabs/puppet/modules/puppet_enterprise/manifests/pxp_agent.pp Line: 105
Corrective change
0670
660
```

This seems to target package_inventory_enabled most frequently. Every run the permission is set from 0674 to 0664, which would seem to correspond with documentation requirements (https://puppet.com/docs/puppet/6.0/resources_file_windows.html#how-nix-modes-map-to-windows-permissions):

> The group can’t have higher permissions than the owner. Other users can’t have higher permissions than the owner or group. (That is, 0640 and 0755 are supported, but 0460 is not.)

However the next agent run shows the value has reverted and needs to be set again. It appears that removing the file often - but not always - resolves the issue.

Ethan Brown (JIRA)

unread,

Nov 30, 2018, 1:51:03 PM11/30/18

to puppe...@googlegroups.com

Ethan Brown updated an issue

Puppet /

Change By:	Ethan Brown
Team:	Windows

Ethan Brown (JIRA)

unread,

Nov 30, 2018, 1:52:02 PM11/30/18

to puppe...@googlegroups.com

Ethan Brown updated an issue

Puppet /

Change By:	Ethan Brown
Sprint:	Windows Grooming

Paul Schaffer (JIRA)

unread,

Nov 30, 2018, 1:53:02 PM11/30/18

to puppe...@googlegroups.com

Paul Schaffer commented on

Re: Puppet sets permissions for Puppet files every run

At least one report shows the group with (F) permissions, which would probably explain the '7' value:

Owner                   : BUILTIN\Administrators

Group                   : NT AUTHORITY\SYSTEM

BUILTIN\Administrators:(R,W,D,WDAC,WO)

NT AUTHORITY\SYSTEM:(F)

Paul Schaffer (JIRA)

unread,

Nov 30, 2018, 1:54:03 PM11/30/18

to puppe...@googlegroups.com

Paul Schaffer updated an issue

Puppet /

Change By:	Paul Schaffer

*Puppet Version:* 2018.1.5, 2019.0.1
*OS Name/Version:* Windows 2012 R2, 2016, 2019

File permissions for Puppet files are being set to the same value every run:

``` {code}

Resource Event Changed from Changed to

File[C:\ProgramData/PuppetLabs/puppet/cache/state/package_inventory_enabled]
File: /opt/puppetlabs/puppet/modules/puppet_enterprise/manifests/profile/agent.pp Line: 89
Corrective change
0674
664

File[C:\ProgramData/PuppetLabs/pxp-agent/etc/pxp-agent.conf]
File: /opt/puppetlabs/puppet/modules/puppet_enterprise/manifests/pxp_agent.pp Line: 105
Corrective change
0670
660

``` {code}

This seems to target package_inventory_enabled most frequently. Every run the permission is set from 0674 to 0664, which would seem to correspond with documentation requirements (https://puppet.com/docs/puppet/6.0/resources_file_windows.html#how-nix-modes-map-to-windows-permissions):

> {panel}

The group can’t have higher permissions than the owner. Other users can’t have higher permissions than the owner or group. (That is, 0640 and 0755 are supported, but 0460 is not.)

{panel}

However the next agent run shows the value has reverted and needs to be set again. It appears that removing the file often - but not always - resolves the issue.

Paul Schaffer (JIRA)

unread,

Nov 30, 2018, 1:54:03 PM11/30/18

to puppe...@googlegroups.com

Paul Schaffer updated an issue

Puppet /

Change By:	Paul Schaffer
CS Priority:	Needs Priority

Paul Schaffer (JIRA)

unread,

Dec 3, 2018, 3:29:04 PM12/3/18

to puppe...@googlegroups.com

Paul Schaffer commented on

Re: Puppet sets permissions for Puppet files every run

A user was able to reproduce these conditions during an upgrade from 5.3.3 to 5.5.8. Notably, when performing the upgrade they observe permissions shifting to a higher level, then the agent run attempting to lower them back down:

With an agent version 5.3.3, prior to upgrade:

C:\WINDOWS\system32>puppet resource file C:\ProgramData\PuppetLabs\puppet\cache\state\package_inventory_enabled

file { 'C:\ProgramData\PuppetLabs\puppet\cache\state\package_inventory_enabled':

...

mode => '0664',

...

C:\WINDOWS\system32>puppet resource file C:\ProgramData\PuppetLabs\pxp-agent\etc\pxp-agent.conf

file { 'C:\ProgramData\PuppetLabs\pxp-agent\etc\pxp-agent.conf':

...

mode => '0660',

...

Immediately following the upgrade to 5.5.8, the permissions have been raised to '0770':

C:\WINDOWS\system32>puppet resource file C:\ProgramData\PuppetLabs\puppet\cache\state\package_inventory_enabled

file { 'C:\ProgramData\PuppetLabs\puppet\cache\state\package_inventory_enabled':

...

mode => '0770',

...

C:\WINDOWS\system32>puppet resource file C:\ProgramData\PuppetLabs\pxp-agent\etc\pxp-agent.conf

file { 'C:\ProgramData\PuppetLabs\pxp-agent\etc\pxp-agent.conf':

...

mode => '0770',

...

And then after the agent run we can see the mismatched '0670':

C:\WINDOWS\system32>puppet resource file C:\ProgramData\PuppetLabs\pxp-agent\etc\pxp-agent.conf

file { 'C:\ProgramData\PuppetLabs\pxp-agent\etc\pxp-agent.conf':

...

mode => '0670',

...

C:\WINDOWS\system32>puppet resource file C:\ProgramData\PuppetLabs\puppet\cache\state\package_inventory_enabled

file { 'C:\ProgramData\PuppetLabs\puppet\cache\state\package_inventory_enabled':

...

mode => '0674',

...

Mike Smith (JIRA)

unread,

Dec 3, 2018, 3:51:03 PM12/3/18

to puppe...@googlegroups.com

Mike Smith updated an issue

Puppet /

Change By:	Mike Smith
Attachment:	image-2018-12-03-12-50-36-742.png

Mike Smith (JIRA)

unread,

Dec 3, 2018, 4:51:03 PM12/3/18

to puppe...@googlegroups.com

Mike Smith updated an issue

Puppet /

Change By:	Mike Smith
Attachment:	image-2018-12-03-13-50-41-861.png

Mike Smith (JIRA)

unread,

Dec 3, 2018, 4:52:03 PM12/3/18

to puppe...@googlegroups.com

Mike Smith updated an issue

Puppet /

Change By:	Mike Smith
Attachment:	image-2018-12-03-13-51-13-968.png

Mike Smith (JIRA)

unread,

Dec 3, 2018, 5:16:03 PM12/3/18

to puppe...@googlegroups.com

Mike Smith updated an issue

Puppet /

Change By:	Mike Smith
Attachment:	image-2018-12-03-14-15-00-161.png

Ethan Brown (JIRA)

unread,

Dec 3, 2018, 7:54:03 PM12/3/18

to puppe...@googlegroups.com

Ethan Brown commented on

Re: Puppet sets permissions for Puppet files every run

In the changelog for 6.0.2 to 6.0.3 at https://github.com/puppetlabs/puppet/compare/6.0.2...6.0.3 I see the change to SYSTEM perm handilng for ~~PUP-9106~~ at https://github.com/puppetlabs/puppet/pull/7088

That seems like the most likely culprit based on current information and we should try to create a minimal repro locally with puppet apply

/cc Glenn Sarti

Paul Schaffer (JIRA)

unread,

Dec 5, 2018, 4:34:02 PM12/5/18

to puppe...@googlegroups.com

Paul Schaffer commented on

Re: Puppet sets permissions for Puppet files every run

It's been reported that for the 6.0.4 agent, while removing the file locally resolves the issue, running the agent via a task causes the permissions issue to reoccur.

Enis Inan (JIRA)

unread,

Dec 5, 2018, 6:45:05 PM12/5/18

to puppe...@googlegroups.com

Enis Inan commented on

Re: Puppet sets permissions for Puppet files every run

I've detected this as well while trying to repro https://tickets.puppetlabs.com/browse/PA-1165. Good to see there's a ticket for it.

Joshua McClintock (JIRA)

unread,

Dec 5, 2018, 6:49:02 PM12/5/18

to puppe...@googlegroups.com

Joshua McClintock commented on

Re: Puppet sets permissions for Puppet files every run

FYI, we 'worked around' this issue, by doing the following:

acl { 'C:/ProgramData/Puppetlabs/pxp-agent/etc/pxp-agent.conf':

group => 'S-1-5-21-1292428093-179605362-682003330-513',

inherit_parent_permissions => false,

owner => 'S-1-5-32-544',

permissions => [

{'identity' => 'BUILTIN\Administrators', 'rights' => ['mask_specific'], 'mask' => '2032031', 'affects' => 'self_only'},

{'identity' => 'GSM1900\Domain Users', 'rights' => ['write', 'read'], 'affects' => 'self_only'},

{'identity' => 'Everyone', 'rights' => ['mask_specific'], 'mask' => '1179776', 'affects' => 'self_only'},

{'identity' => 'NT AUTHORITY\SYSTEM', 'rights' => ['full'], 'affects' => 'self_only'}],

require => File['C:\ProgramData/PuppetLabs/pxp-agent/etc/pxp-agent.conf'],

}

acl { 'C:\ProgramData/PuppetLabs/puppet/cache/state/package_inventory_enabled':

group => 'S-1-5-21-1292428093-179605362-682003330-513',

inherit_parent_permissions => false,

owner => 'S-1-5-32-544',

permissions => [

{'identity' => 'BUILTINAdministrators', 'rights' => ['mask_specific'], 'mask' => '2032031', 'affects' => 'self_only'}

,

{'identity' => 'GSM1900\Domain Users', 'rights' => ['write', 'read'], 'affects' => 'self_only'}

,

{'identity' => 'Everyone', 'rights' => ['read'], 'affects' => 'self_only'}

,

{'identity' => 'NT AUTHORITY\SYSTEM', 'rights' => ['full'], 'affects' => 'self_only'}

],

require => File['C:\ProgramData/PuppetLabs/puppet/cache/state/package_inventory_enabled'],

}

Adam Bottchen (JIRA)

unread,

Dec 6, 2018, 7:30:03 PM12/6/18

to puppe...@googlegroups.com

Adam Bottchen updated an issue

Puppet /

Change By:	Adam Bottchen
CS Priority:	Needs Priority Reviewed

Erick Banks (JIRA)

unread,

Dec 11, 2018, 6:41:04 PM12/11/18

to puppe...@googlegroups.com

Erick Banks updated an issue

Puppet /

Change By:	Erick Banks
Acceptance Criteria:	Patched back to 5.5. Manual testing (recommend Functional Review). Work involved: Code (change), maaaaaybe docs

Erick Banks (JIRA)

unread,

Dec 11, 2018, 6:44:04 PM12/11/18

to puppe...@googlegroups.com

Erick Banks updated an issue

Puppet /

Change By:	Erick Banks
Story Points:	1
Sprint:	Windows Grooming Hopper

Mike Smith (JIRA)

unread,

Dec 12, 2018, 1:48:05 PM12/12/18

to puppe...@googlegroups.com

Mike Smith commented on

Re: Puppet sets permissions for Puppet files every run

To restate when I was testing - deleting file and letting puppet recreate resolves issue (is a workaround)

Eric Thompson (JIRA)

unread,

Jan 2, 2019, 4:29:03 PM1/2/19

to puppe...@googlegroups.com

Eric Thompson commented on

Re: Puppet sets permissions for Puppet files every run

hi y'all. please set a fix version when we know where the fix will go. hopefully this will prevent tickets like this getting lost or not prioritized when they are no longer associated with a (closed) support escalation.

Eric Thompson (JIRA)

unread,

Jan 18, 2019, 12:57:06 PM1/18/19

to puppe...@googlegroups.com

Eric Thompson updated an issue

Puppet /

Change By:	Eric Thompson
Labels:	escal

Eric Thompson (JIRA)

unread,

Jan 18, 2019, 12:57:06 PM1/18/19

to puppe...@googlegroups.com

Eric Thompson (JIRA)

unread,

Jan 18, 2019, 12:57:07 PM1/18/19

to puppe...@googlegroups.com

Eric Thompson updated an issue

Puppet /

Change By:	Eric Thompson
Labels:	escalation

Eric Thompson (JIRA)

unread,

Jan 23, 2019, 4:08:06 PM1/23/19

to puppe...@googlegroups.com

Eric Thompson updated an issue

Puppet /

Comment:
Change By:	Eric Thompson

hi y'all. please set a fix version when we know where the fix will go. hopefully this will prevent tickets like this getting lost or not prioritized when they are no longer associated with a (closed) support escalation.

Adam Bottchen (JIRA)

unread,

Jan 23, 2019, 5:00:08 PM1/23/19

to puppe...@googlegroups.com

Adam Bottchen updated an issue

Puppet /

Change By:	Adam Bottchen
CS Priority:	Reviewed Major

Eric Thompson (JIRA)

unread,

Jan 30, 2019, 4:12:05 PM1/30/19

to puppe...@googlegroups.com

Eric Thompson updated an issue

Puppet /

Change By:	Eric Thompson
Priority:	Normal Major

Eric Thompson (JIRA)

unread,

Feb 6, 2019, 2:33:05 PM2/6/19

to puppe...@googlegroups.com

Eric Thompson commented on

Re: Puppet sets permissions for Puppet files every run

Keiran Haggerty this is starting to impact more and more customers. any ideas on the relative priority of this and chances to get it into the next Z?

fyi Jed Gresham

Sean McDonald (JIRA)

unread,

Feb 12, 2019, 2:24:07 PM2/12/19

to puppe...@googlegroups.com

Sean McDonald updated an issue

Puppet /

Change By:	Sean McDonald
Sprint:	Windows Hopper Platform OS Kanban

Sean McDonald (JIRA)

unread,

Feb 12, 2019, 2:24:07 PM2/12/19

to puppe...@googlegroups.com

Sean McDonald updated an issue

Puppet /

Change By:	Sean McDonald
Team:	Windows Platform OS

Sean McDonald (JIRA)

unread,

Feb 12, 2019, 2:24:08 PM2/12/19

to puppe...@googlegroups.com

Sean McDonald assigned an issue to Sean McDonald

Puppet /

Change By:	Sean McDonald
Assignee:	Sean McDonald

Josh Cooper (JIRA)

unread,

Feb 14, 2019, 12:48:04 PM2/14/19

to puppe...@googlegroups.com

Josh Cooper commented on

Re: Puppet sets permissions for Puppet files every run

Couple of general comments. The change in behavior is due to ~~PUP-9106~~. Second, if puppet is running as System (aka LocalSystem), I would expect files created by that account to default to Owner=Administrators (the local group!) and Group=System, based on its default DACL. I don't think puppet should automatically guess or change that behavior.

I think we need to consider the cases where the owner and/or group are explicitly managed, eg group => 'System' versus not managed.

If the owner/group is not managed (as described in this ticket), then I would expect puppet to special case the System account, such that it considers mode to be insync if System has FullControl, and basically ignore what the manifest says. This way if the manifest says mode => 0664 and System has FullControl, then it should be insync. The only time it wouldn't be insync is if there isn't a System ACE at all, the ACE(s) for System grants less than FullControl, or it's a deny ACE.

If System is explicitly managed, eg group => 'System', then I would expect puppet to set whatever mode is specified, even if it's less than FullControl. However, if the mode is less than FullControl, then we should probably emit a warning, saying that's a bad idea.

Kerry Halpin (JIRA)

unread,

Feb 21, 2019, 6:37:04 PM2/21/19

to puppe...@googlegroups.com

Kerry Halpin commented on

Re: Puppet sets permissions for Puppet files every run

I have noticed that the file resource mode attribute is trying to add a local 'NONE' group that has a SID of S-1-5-21-<domain identifier which does not match ours>-513, which is the Domain Users SID of some unknown domain. I'm thinking this was supposed to dynamically map to our domain's "Domain Users" group, but a static value was left in it. Somehow, probably coincidence, I think Windows also has a "feature" that translates a hard-coded domain SID as 'None' when the SID does not match a known domain. Is the agent setting the mode via an explicit DACL configuration, e.g. using ICACLS?

Kerry Halpin (JIRA)

unread,

Feb 22, 2019, 11:59:05 AM2/22/19

to puppe...@googlegroups.com

Kerry Halpin updated an issue

Puppet /

Change By:	Kerry Halpin
Attachment:	NoneSIDerror.png

Kerry Halpin (JIRA)

unread,

Feb 22, 2019, 12:02:08 PM2/22/19

to puppe...@googlegroups.com

Kerry Halpin commented on

Re: Puppet sets permissions for Puppet files every run

Some clarification:
The "None" SID that you see below is indeed a windows "feature". We are able to add it on any windows server, regardless of whether it is puppet managed - it does not show up as a builtin group, but if you search for it to add it to an ACL through the GUI, windows will find "None" and use it. The domain identifier portion of the "None" SID is randomized at a per-server level it appears. Looking at Joshua McClintock's post, I noticed that he sees the "Domain Users" group where we are seeing the "None" group. My best guess at this point is that the file mode is supposed to be setting "Domain Users", but in our environment "Domain Users" is not being found, so Windows is substituting the "None" principle.
Regardless, we have seen some of our test nodes still manage to set the permission on the none group and move to an unchanged state (no more thrashing), but in our dev environment, Puppet is attempting to make the change every time as others are reporting. Puppet is attempting to change the mode from '0670' to '0660'

Geoff Nichols (JIRA)

unread,

Feb 27, 2019, 2:05:09 PM2/27/19

to puppe...@googlegroups.com

Geoff Nichols updated an issue

Puppet /

Change By:	Geoff Nichols
Sprint:	Platform OS Kanban , Skeletor Kanban

Sean McDonald (JIRA)

unread,

Feb 27, 2019, 2:51:06 PM2/27/19

to puppe...@googlegroups.com

Sean McDonald commented on

Re: Puppet sets permissions for Puppet files every run

Kenn Hussey yeah, the PR is meant as a fix

Sean McDonald (JIRA)

unread,

Feb 27, 2019, 2:52:06 PM2/27/19

to puppe...@googlegroups.com

Sean McDonald updated an issue

Puppet /

Change By:	Sean McDonald
Fix Version/s:	PUP 6.0.6
Fix Version/s:	PUP 5.5.11

Geoff Nichols (JIRA)

unread,

Mar 12, 2019, 6:31:05 PM3/12/19

to puppe...@googlegroups.com

Geoff Nichols commented on

Re: Puppet sets permissions for Puppet files every run

Sean McDonald, please provide release notes for this issue, if needed. Thanks!

Sean McDonald (JIRA)

unread,

Mar 12, 2019, 7:26:04 PM3/12/19

to puppe...@googlegroups.com

Sean McDonald updated an issue

Puppet /

Change By:	Sean McDonald
Release Notes:	Bug Fix

Sean McDonald (JIRA)

unread,

Mar 12, 2019, 7:31:07 PM3/12/19

to puppe...@googlegroups.com

Sean McDonald updated an issue

Puppet /

Change By:

Sean McDonald

Release Notes Summary:

Puppet will now treat owner and group on the file resource as in-sync in the following scenario:

* owner/group are not set in the resource
* owner/group are set to the SYSTEM user
* the SYSTEM user ACE is set to Full Control

Puppet will allow users to specifically configure the SYSTEM user to less than FullControl by setting the owner and/or group parameters to 'SYSTEM' in the file resource. (i.e. if owner and/or group are set to 'SYSTEM' puppet will _not_ munge permissions to FullControl). In this case Puppet will emit a warning since setting SYSTEM to less than FullControl may have unintended consequences.

Sean McDonald (JIRA)

unread,

Mar 12, 2019, 7:32:05 PM3/12/19

to puppe...@googlegroups.com

Sean McDonald updated an issue

Puppet /

Change By:	Sean McDonald
Release Notes Summary:

Puppet will now treat owner and group on the file resource as in-sync in the following scenario:

* owner / and group are not set in the resource
* owner and / or group are set to the SYSTEM user on the running node.

* the SYSTEM user ACE is set to Full Control

Puppet will allow users to specifically configure the SYSTEM user to less than FullControl by setting the owner and/or group parameters to 'SYSTEM' in the file resource. (i.e. if owner and/or group are set to 'SYSTEM' puppet will _not_ munge permissions to FullControl). In this case Puppet will emit a warning since setting SYSTEM to less than FullControl may have unintended consequences.

Geoff Nichols (JIRA)

unread,

Mar 13, 2019, 2:25:08 PM3/13/19

to puppe...@googlegroups.com

Geoff Nichols updated an issue

Puppet /

Change By:	Geoff Nichols
Sprint:	Platform OS Kanban, Skeletor Kanban , Skeletor Kanban

Heston Hoffman (JIRA)

unread,

Mar 16, 2019, 10:18:03 PM3/16/19

to puppe...@googlegroups.com

Heston Hoffman updated an issue

Puppet /

Change By:	Heston Hoffman
Labels:	escalation resolved-issue-added

Fredrik Nilsson (JIRA)

unread,

Mar 19, 2019, 5:43:04 AM3/19/19

to puppe...@googlegroups.com

Fredrik Nilsson commented on

Re: Puppet sets permissions for Puppet files every run

Hi Guys,

Same issue, different files....

/Stage[main]/Puppet::Config/Concat[C:/ProgramData/PuppetLabs/puppet/etc/puppet.conf]/File[C:/ProgramData/PuppetLabs/puppet/etc/puppet.conf]/mode

mode changed '0674' to '0644'

I've come to the unsupported conclusion, not looking into it that is a fact, but that this occur on all our newly installed machines from a certain date (unknown) until present.

I have another file that has the same behavior, but it is outside Puppets folder structure, but the file itself is managed by puppet. Not all machines having the above mentioned problem has the equal problem with this second file, but the great majority has...

/Stage[main]/Splunk/Concat[C:/Program Files/SplunkUniversalForwarder/etc/auth/liuit/puppetpki-~~[SERVERNAME].pem]/File[C:/Program Files/SplunkUniversalForwarder/etc/auth/liuit/puppetpki~~-[SERVERNAME].pem]/mode

mode changed '0674' to '0644'

If you need more information please let me know if I can help!

Eric Thompson (JIRA)

unread,

Apr 12, 2019, 2:54:04 PM4/12/19

to puppe...@googlegroups.com

Eric Thompson assigned an issue to Eric Thompson

Puppet /

Change By:	Eric Thompson
Assignee:	Sean McDonald Eric Thompson

Eric Thompson (JIRA)

unread,

Apr 12, 2019, 2:55:06 PM4/12/19

to puppe...@googlegroups.com

Eric Thompson assigned an issue to Unassigned

Puppet /

Change By:	Eric Thompson
Assignee:	Eric Thompson

Jesse Reynolds (JIRA)

unread,

May 1, 2019, 3:46:03 AM5/1/19

to puppe...@googlegroups.com

Jesse Reynolds commented on

Re: Puppet sets permissions for Puppet files every run

I am surprised this issue didn't get a mention in the 2019.0.3 release notes (that i can see)

Mike Smith (JIRA)

unread,

May 1, 2019, 9:27:04 AM5/1/19

to puppe...@googlegroups.com

Mike Smith commented on

Re: Puppet sets permissions for Puppet files every run

Jesse Reynolds I was looking and was unsure if it should since it was resolved in a previous release of the agent software if I recall (like 6.0.7 vs 6.0.9 being packaged here)

Sean McDonald (JIRA)

unread,

May 6, 2019, 12:41:06 PM5/6/19

to puppe...@googlegroups.com

Sean McDonald commented on

Re: Puppet sets permissions for Puppet files every run

yeah, I will work on it with her

Sean McDonald (JIRA)

unread,

May 6, 2019, 12:57:03 PM5/6/19

to puppe...@googlegroups.com

Sean McDonald commented on

Re: Puppet sets permissions for Puppet files every run

https://tickets.puppetlabs.com/browse/PE-26477 has been created to track this work in the PE space.

Matt Baylis (JIRA)

unread,

Jun 24, 2019, 1:27:05 AM6/24/19

to puppe...@googlegroups.com

Matt Baylis updated an issue

Puppet /

Change By:	Matt Baylis
Attachment:	image-2019-06-24-15-26-33-971.png

Matt Baylis (JIRA)

unread,

Jun 24, 2019, 1:28:05 AM6/24/19

to puppe...@googlegroups.com

Matt Baylis commented on

Re: Puppet sets permissions for Puppet files every run

I see this issue as well within my environment, v2018.1.7

seems to be happening on server 2012 R2 servers

Thomas Kishel (JIRA)

unread,

Jul 29, 2019, 5:21:04 PM7/29/19

to puppe...@googlegroups.com

Thomas Kishel commented on

Re: Puppet sets permissions for Puppet files every run

This is marked as fixed in Puppet 5.5.12 so PE 2018.1.8 (which ships with 5.5.14) or newer, as per ... https://puppet.com/docs/pe/2019.1/component_versions_in_recent_pe_releases.html

Austin Boyd (JIRA)

unread,

Dec 12, 2019, 8:51:05 AM12/12/19

to puppe...@googlegroups.com

Austin Boyd updated an issue

Puppet /

Change By:	Austin Boyd
Zendesk Ticket IDs:	33181
Zendesk Ticket Count:	1

Austin Boyd (JIRA)

unread,

Dec 12, 2019, 8:52:09 AM12/12/19

to puppe...@googlegroups.com

Austin Boyd updated an issue

Puppet /

Change By:	Austin Boyd
Zendesk Ticket IDs:	32929, 33181
Zendesk Ticket Count:	1 2

Austin Boyd (JIRA)

unread,

Dec 12, 2019, 8:52:11 AM12/12/19

to puppe...@googlegroups.com

Austin Boyd updated an issue

Puppet /

Change By:	Austin Boyd
Zendesk Ticket IDs:	32929, 32969, 33181
Zendesk Ticket Count:	2 3

Austin Boyd (JIRA)

unread,

Dec 12, 2019, 8:52:14 AM12/12/19

to puppe...@googlegroups.com

Austin Boyd updated an issue

Puppet /

Change By:	Austin Boyd
Zendesk Ticket IDs:	32929,32969, 33126, 33181
Zendesk Ticket Count:	3 4

Austin Boyd (JIRA)

unread,

Dec 12, 2019, 8:52:15 AM12/12/19

to puppe...@googlegroups.com

Austin Boyd updated an issue

Puppet /

Change By:	Austin Boyd
Zendesk Ticket IDs:	32929,32969, 33124, 33126,33181
Zendesk Ticket Count:	4 5

Austin Boyd (JIRA)

unread,

Dec 12, 2019, 8:52:16 AM12/12/19

to puppe...@googlegroups.com

Austin Boyd updated an issue

Puppet /

Change By:	Austin Boyd
Zendesk Ticket IDs:	32929,32969, 33091, 33124,33126,33181
Zendesk Ticket Count:	5 6

Austin Boyd (JIRA)

unread,

Dec 12, 2019, 8:54:04 AM12/12/19

to puppe...@googlegroups.com

Austin Boyd updated an issue

Puppet /

Change By:	Austin Boyd
Zendesk Ticket IDs:	32929,32969,33091,33124,33126,33181 ,33410
Zendesk Ticket Count:	6 7

Austin Boyd (JIRA)

unread,

Dec 12, 2019, 8:55:08 AM12/12/19

to puppe...@googlegroups.com

Austin Boyd updated an issue

Puppet /

Change By:	Austin Boyd
Zendesk Ticket IDs:	32929,32969,33091,33124,33126,33181,33410 ,33732
Zendesk Ticket Count:	7 8

Austin Boyd (JIRA)

unread,

Dec 12, 2019, 8:55:10 AM12/12/19

to puppe...@googlegroups.com

Austin Boyd updated an issue

Puppet /

Change By:	Austin Boyd
Zendesk Ticket IDs:	32929,32969,33091,33124,33126,33181,33410,33732 ,33886
Zendesk Ticket Count:	8 9

Austin Boyd (JIRA)

unread,

Dec 12, 2019, 8:55:10 AM12/12/19

to puppe...@googlegroups.com

Austin Boyd updated an issue

Puppet /

Change By:	Austin Boyd
Zendesk Ticket IDs:	32929,32969,33091,33124,33126,33181,33410,33732,33886 ,33925
Zendesk Ticket Count:	9 10

Austin Boyd (JIRA)

unread,

Dec 12, 2019, 8:57:04 AM12/12/19

to puppe...@googlegroups.com

Austin Boyd updated an issue

Puppet /

Change By:	Austin Boyd
Zendesk Ticket IDs:	32929,32969,33091,33124,33126,33181,33410,33732,33886,33925 ,34080
Zendesk Ticket Count:	10 11

Austin Boyd (JIRA)

unread,

Dec 12, 2019, 8:58:07 AM12/12/19

to puppe...@googlegroups.com

Austin Boyd updated an issue

Puppet /

Change By:	Austin Boyd
Zendesk Ticket IDs:	32929,32969,33091,33124,33126,33181,33410,33732,33886,33925,34080 ,34309
Zendesk Ticket Count:	11 12

Austin Boyd (JIRA)

unread,

Dec 12, 2019, 8:58:09 AM12/12/19

to puppe...@googlegroups.com

Austin Boyd updated an issue

Puppet /

Change By:	Austin Boyd
Zendesk Ticket IDs:	32929,32969,33091,33124,33126,33181,33410,33732,33886,33925,34080,34309 ,34367
Zendesk Ticket Count:	12 13

Austin Boyd (JIRA)

unread,

Dec 12, 2019, 8:59:06 AM12/12/19

to puppe...@googlegroups.com

Austin Boyd updated an issue

Puppet /

Change By:	Austin Boyd
Zendesk Ticket IDs:	32929,32969,33091,33124,33126,33181,33410,33732,33886,33925,34080,34309,34367 ,34392
Zendesk Ticket Count:	13 14

Austin Boyd (JIRA)

unread,

Dec 12, 2019, 9:00:08 AM12/12/19

to puppe...@googlegroups.com

Austin Boyd updated an issue

Puppet /

Change By:	Austin Boyd
Zendesk Ticket IDs:	32929,32969,33091,33124,33126,33181,33410,33732,33886,33925,34080,34309,34367,34392 ,34426
Zendesk Ticket Count:	14 15

Austin Boyd (JIRA)

unread,

Dec 12, 2019, 9:01:07 AM12/12/19

to puppe...@googlegroups.com

Austin Boyd updated an issue

Puppet /

Change By:	Austin Boyd
Zendesk Ticket IDs:	32929,32969,33091,33124,33126,33181,33410,33732,33886,33925,34080,34309,34367,34392,34426,34455 ,34555
Zendesk Ticket Count:	16 17

Austin Boyd (JIRA)

unread,

Dec 12, 2019, 9:01:07 AM12/12/19

to puppe...@googlegroups.com

Austin Boyd updated an issue

Puppet /

Change By:	Austin Boyd
Zendesk Ticket IDs:	32929,32969,33091,33124,33126,33181,33410,33732,33886,33925,34080,34309,34367,34392,34426 ,34455

Zendesk Ticket Count:	15 16

Austin Boyd (JIRA)

unread,

Dec 12, 2019, 9:02:08 AM12/12/19

to puppe...@googlegroups.com

Austin Boyd updated an issue

Puppet /

Change By:	Austin Boyd
Zendesk Ticket IDs:	32929,32969,33091,33124,33126,33181,33410,33732,33886,33925,34080,34309,34367,34392,34426,34455,34555 ,34784
Zendesk Ticket Count:	17 18

Austin Boyd (JIRA)

unread,

Dec 12, 2019, 9:02:10 AM12/12/19

to puppe...@googlegroups.com

Austin Boyd updated an issue

Puppet /

Change By:	Austin Boyd
Zendesk Ticket IDs:	32929,32969,33091,33124,33126,33181,33410,33732,33886,33925,34080,34309,34367,34392,34426,34455,34555,34784,35321 ,35693
Zendesk Ticket Count:	19 20

Austin Boyd (JIRA)

unread,

Dec 12, 2019, 9:02:11 AM12/12/19

to puppe...@googlegroups.com

Austin Boyd updated an issue

Puppet /

Change By:	Austin Boyd
Zendesk Ticket IDs:	32929,32969,33091,33124,33126,33181,33410,33732,33886,33925,34080,34309,34367,34392,34426,34455,34555,34784 ,35321

Zendesk Ticket Count:	18 19

Austin Boyd (Jira)

unread,

May 21, 2021, 1:28:02 AM5/21/21

to puppe...@googlegroups.com

Austin Boyd updated an issue

Puppet /

Change By:	Austin Boyd
Labels:	escalation jira_escalated resolved-issue-added

This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)

Austin Boyd (Jira)

unread,

May 21, 2021, 1:28:02 AM5/21/21

to puppe...@googlegroups.com

Austin Boyd updated an issue

Puppet /

Change By:	Austin Boyd
Zendesk Ticket Count:	20 21
Zendesk Ticket IDs:	32929,32969,33091,33124,33126,33181,33410,33732,33886,33925,34080,34309,34367,34392,34426,34455,34555,34784,35321,35693 ,44391

Austin Boyd (Jira)

unread,

May 23, 2021, 11:14:05 PM5/23/21

to puppe...@googlegroups.com

Austin Boyd updated an issue

Puppet /

Change By:	Austin Boyd
Zendesk Ticket Count:	21 22
Zendesk Ticket IDs:	32929,32969,33091,33124,33126,33181,33410,33732,33886,33925,34080,34309,34367,34392,34426,34455,34555,34784,35321,35693, 44389, 44391