-
-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
metadata.json permissions changed between v2.0.5 and v2.0.7 #9
Comments
I've pushed v.2.0.8 to the forge, can you verify if the issue is solved? |
On both a test PE 3.8.2 master and my workstation, v2.0.8 pulls down with a metadata.json that is still 0400. |
I've made some mess with the umask on the machine where modules were packed and pushed. |
Looks good. Thanks! On Mon, Oct 19, 2015 at 8:28 AM Alessandro Franceschi <
|
I'm upgrading the modules in our site's Puppetfile and was upgrading this module from v2.0.5 to v2.0.7. It caused the following error:
Error: /File[/var/opt/lib/pe-puppet/facts.d]: Failed to generate additional resources using 'eval_generate': Error 400 on SERVER: Permission denied - /etc/puppetlabs/puppet/environments/feature_PUP439_tecontrol/modules/rclocal/metadata.json
Error: /File[/var/opt/lib/pe-puppet/facts.d]: Could not evaluate: Could not retrieve file metadata for puppet://puppetsandbox.tycoelectronics.net/pluginfacts: Error 400 on SERVER: Permission denied - /etc/puppetlabs/puppet/environments/feature_PUP439_tecontrol/modules/rclocal/metadata.json
Comparing the file permissions of metadata.json for the two releases:
v2.0.5:
-r--r--r-- 1 root root 931 Oct 25 2013 metadata.json
v2.0.7:
-r-------- 1 root root 521 Aug 18 09:45 metadata.json
The change in metadata.json file permissions is causing this issue.
I would put in a PR to change this, but you haven't included metadata.json in this repo. You must be adding it when publishing the module to the Forge.
Thanks.
The text was updated successfully, but these errors were encountered: