Jira (PUP-7102) Insufficient logging when encountering 'permission denied' on environmentpath

[Josh Cooper (JIRA)]

Title: Message Title

Josh Cooper commented on PUP-7102   Re: Insufficient logging when encountering 'permission denied' on environmentpath One thing I noticed is that if the permissions are incorrect on one of the ancestor directories then puppetserver will fail to start: 06:01:52 Feb 21 06:01:21 rbjkogu91d1gagw systemd[1]: Starting puppetserver Service... 06:01:52 Feb 21 06:01:21 rbjkogu91d1gagw puppetserver[13389]: OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 06:01:52 Feb 21 06:01:50 rbjkogu91d1gagw puppetserver[13389]: Errno::EACCES: Permission denied - /tmp/lookup_test_dir.hZDf2k 06:01:52 Feb 21 06:01:50 rbjkogu91d1gagw puppetserver[13389]: valid_directory? at /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/environments.rb:242 This is different than the compilation will fail with HTTP 500 during catalog compilation. I'm not sure if that was because the test created a temp codedir directory owned by root:root and mode 700 (as opposed to a directory at a lower level, like $codedir/environments/<environment>). If the behavior is expected (for puppetserver to fail to start), then we should make sure to release note it. Add Comment   This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.