Jira (PUP-3185) A puppet-passenger master fails with cryptic message for default directory environment setup with non-existent production directory.

[Franz Pletz (JIRA)]

Title: Message Title

Franz Pletz commented on an issue   Re: A puppet-passenger master fails with cryptic message for default directory environment setup with non-existent production directory. Is it actually necessary to create the environment directory for the environment the master is theoretically configured through puppet.conf? Shouldn't the environment setting be irrelevant for the master? The agents can query the master for other environments which are allowed to not exist at all and still return a meaningful response: Error: Could not retrieve catalog from remote server: Find /adkljsdlads/catalog/puppet.localdomain?facts_format=pson&facts=%257B%2522name%2522%253A%2522pupp... resulted in 404 with the message: Not Found: Could not find environment 'adkljsdlads' Add Comment   Puppet / PUP-3185 A puppet-passenger master fails with cryptic message for default directory environment setup with non-existent production directory. PUP-2519 changed the settings catalog to create the default directory environment. [~fpletz] noticed that for a puppet master running under passenger, this can cause problems (and does with the default puppetmaster-passenger package on Debian) if the user the rack process is running as does not have permission to create the production directory. You e... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.