Issue #10269 has been updated by Jacob Helwig.
Status changed from In Topic Branch Pending Review to Merged - Pending Release
Assignee deleted (Josh Cooper)
Target version changed from 2.7.x to 2.7.7
The fix for this has been merged into 2.7.x in
commit:4e1e75581ccf82a2244bec026bd4ffbf011704bc
commit 8576e868be0eeda8acbb28f4a8e69ce9c12552b3
Author: Josh Cooper <[email protected]>
Date: Mon Oct 31 11:23:20 2011
(#10269) Search bit not set on newly created directories
Previously, puppet would not set the user, group, or other
execute/search bits for newly created directories. This was a
regression introduced in 2.7.6 in commit
22bfd9ce83ff52d909a43c370ba71112ed4961a4.
This was caused because the dirmask'ing was occurring when munging the
mode property, but that was occurring prior to the ensure property
being synced, which is when the directory is actually created. And
since the directory did not exist, the executable bits were never
added.
Similar failures would occur if the path referred to a non-executable
file or link that we wanted to change to a directory.
This commit reverts the changes to the dirmask and munge methods, and
moves the call to dirmask back to the retrieve method. This way we can
be sure that the directory has been created by the time we call
dirmask.
Ideally, we could know at munge time whether we are going to create a
directory as opposed to a file or link. But the logic for that depends
on many other properties, e.g. source, target, etc. The easiest thing
is to just revert the change.
Paired-with: Nick Lewis <[email protected]>
----------------------------------------
Bug #10269: When creating directories, puppet does not set the search/traverse
bit with read permission bit
https://projects.puppetlabs.com/issues/10269
Author: Justin Bronn
Status: Merged - Pending Release
Priority: Urgent
Assignee:
Category: file
Target version: 2.7.7
Affected Puppet version: 2.7.6
Keywords: file mode permission
Branch: https://github.com/puppetlabs/puppet/pull/189
There's been a regression with file resources in 2.7.6. For example, let's say
you have the following in a manifest called 'bug.pp':
file { "/tmp/newdir":
ensure => directory,
mode => '0600',
}
After applying the manifest, this is what the directory permissions look like:
$ ls -l /tmp/newdir
drw-------. 2 root root 4096 Oct 25 10:37 newdir
Needless to say, this can cause havoc on manifests and other resource types
that need to change into the created directory.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
