Jira (PUP-8383) /opt/puppetlabs/puppet/cache/facts.d]/mode: mode changed '0755' to '0777'
Title: Message Title BellaX assigned an issue to Henrik Lindberg Hi Henrik, this is how I reproduced the issue on a brand new puppet master, simply create a folder in /etc/puppetlabs/code/environments/production/modules/test, and then 'chmod 777 /etc/puppetlabs/code/environments/production/modules/test', add the path "modulepath = ./modules/test:$basemodulepath" in /etc/puppetlabs/code/environments/production/environment.conf, run 'puppet agent -t' The puppet master I installed is "puppet-enterprise-2017.3.2-ubuntu-16.04-amd64", the host is a Ubuntu VM. Of course there is no way any of the modules folder would be set to 777 in reality, it happened due to a misuse of a param when syncing the files from code repo. However, no matter the mode of the module folder is 777 or not, it should not affect /opt/puppetlabs. Puppet / PUP-8383 /opt/puppetlabs/puppet/cache/facts.d]/mode: mode changed '0755' to '0777' Change By: BellaX Assignee: BellaX Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this
Jira (PUP-8383) /opt/puppetlabs/puppet/cache/facts.d]/mode: mode changed '0755' to '0777'
Title: Message Title BellaX created an issue Puppet / PUP-8383 /opt/puppetlabs/puppet/cache/facts.d]/mode: mode changed '0755' to '0777' Issue Type: Bug Affects Versions: PUP 5.3.3 Assignee: Unassigned Components: Catalog Application Created: 2018/01/23 10:03 PM Priority: Normal Reporter: BellaX Puppet Version: 5.3.3 Puppet Server Version: PE 2017.3 OS Name/Version: Ubuntu 16.4 'puppet agent -t' changed /opt/puppetlabs/puppet/cache/facts.d]/mode to 0777. This happens on nodes with no custom code yet. Here is the command line output: Info: Using configured environment 'production' Info: Retrieving pluginfacts Notice: /File[/opt/puppetlabs/puppet/cache/facts.d]/mode: mode changed '0755' to '0777' Info: Retrieving plugin Info: Loading facts Info: Caching catalog for puppet.local Info: Applying configuration version '1516773686' Notice: Applied catalog in 11.56 seconds
Jira (PUP-7164) The yaml_data function used by lookup should return empty hash for empty yaml files
Title: Message Title
BellaX commented on PUP-7164
Re: The yaml_data function used by lookup should return empty hash for empty yaml files
Hi Henrik Lindberg, is it same fix to the error of Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Function lookup() did not find a value for the name 'profile::webserver_lnp::logrotate_rules' on node ***? I didn't specify any key 'profile::webserver_lnp::logrotate_rules' yet in any yaml file, I just wanted to see how it would behave if the key does not exist. In the manifest file, I did: $real_logrotate_rules = deep_merge($logrotate_rules, lookup('profile::webserver_lnp::logrotate_rules', {merge => 'deep'}
)) however, when I replacing "lookup" with "hiera_hash", it did not throw error.
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
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 puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
