default umask makes installed modules inaccessible

[igalic]

igalic@puppet01 ~ % sudo ls -lahrt /etc/puppet/environments/production/modules/bundler
total 32K
drwx------   2  502 staff 4.0K Feb  1  2013 templates
-rw-------   1  502 staff  819 Feb  1  2013 metadata.json
-rw-------   1  502 staff  264 Feb  1  2013 README.markdown
-rw-------   1  502 staff  270 Feb  1  2013 Modulefile
-rw-------   1  502 staff  552 Feb  1  2013 LICENSE
drwx------   4  502 staff 4.0K Feb  1  2013 .
drwx------   2  502 staff 4.0K Aug 13 16:36 manifests
drwxr-xr-x 105 root root  4.0K Aug 13 16:36 ..
igalic@puppet01 ~ %  

resulting in:

Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Permission denied - /etc/puppet/environments/production/modules/bundler/manifests/init.pp on node log01.misc.dev.rz01.riseops.at
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
1 igalic@log01 ~ %

[maxenced]

Also hit this issue, only happen with this module, not sure why ...

[igalic]

It hits many of the modules originally authored by @adrienthebo ;) because of the way he has his home directory setup, and thus way he releases modules/gems.

[frozenfoxx]

Hit this myself as well. Temporarily doing a chmod on the files once pulled down to add group and other read permissions works through continuous updates. I.E. after you've chmodded the files once as long as there's no new files later updates through puppet module install OR through git updates will continue to leave the new permissions intact so you don't need to change your deployment pipeline while waiting for a fix at the module level.

[netors]

same problem here, temporary fix using:

# chmod g+r -R modules/bundler

[stevelacey]

+1

[igalic]

my fix is generally to install from git.

[neoice]

I use librarian-puppet and just hit this issue. I used to install via git but librarian-puppet is so amazing, it's changed my workflow and freed me from the pain of git submodule and hacky shellscripts to git clone.

[zachfi]

I'd happily review a PR. You can see that this module does not get updated very often. It serves a small purpose for us internally, and it rarely needs changing so issues like this are not caught and fixed.

[neoice]

does the module published on forge match this code?

I forked, cloned and got the correct permissions. if I recall, git permissions are not true UNIX permissions, but I don't remember exactly what differs.

[stevelacey]

I think the permissions in the repo are fine, git does store them, and as far as I know they are as per UNIX permissions- but they look fine in this case.

My best guess is that this repo isn't what is deployed to the forge. I expect the tarball was manually packaged and the permissions were wrong when it was?

[zachfi]

I'll post an update to the forge.

[zachfi]

1.0.1 has just been pushed to the forge. Please upgrade and let me know if this is still an issue.