Issue #21291 has been reported by Mariusz Gronczewski.

----------------------------------------
Bug #21291: Puppet changes file permissions when sourcing files from fileserver
https://projects.puppetlabs.com/issues/21291

* Author: Mariusz Gronczewski
* Status: Unreviewed
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* Affected Puppet version: 3.1.1
* Keywords: 
* Branch: 
----------------------------------------
We started migration from SVN to Git, and along the way we tightened 
permissions to files, making separate user for syncing manifests.

In effect, our manifests were owned by root but now are owned by "normal" user.

Switching repositories resulted in:

    
/Stage[init]/Artegence::Common/File[/etc/profile.d/zzz-user-prompt.sh]/owner) 
owner changed 'root' to '20114500'

and a lot of "mode changed '0664' to '0644'"
in resources that have not defined mode and user, like in:

        file { "/etc/profile.d/zzz-user-prompt.sh":
            ensure   => present,
            source   => "puppet://puppet/modules/artegence/zzz-user-prompt.sh",

Basically, file permissions when sourcing files are defaulted to SOURCE 
permissions instead of actual TARGET permissions
but when using templates/content, files are defaulted to TARGET permissions, 
which can cause very "fun" and interesting stuff

Expected behaviour would be to:
* not change existing file permissions
* do not inherit them from fileserver but use same permissions as file which 
uses 'content' instead of source





-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to