Error on new node with non-production environment

asked 2016-06-02 10:34:52 -0600

gerhard gravatar image


I installed Puppet on a Windows machine with the environment automatically set to a custom environment (development). Since Puppet 4 (PE 2016.1) this is causing problems – I'm getting errors about the environment that cannot be found, e.g.: /File[C:/ProgramData/PuppetLabs/puppet/cache/facts.d]: Failed to generate additional resources using 'eval_generate': Error 400 on SERVER: Could not find environment 'development'

This has the effect of Marionette not being able to initialise properly. The workaround seems to be to either deploy ‘production’ first (and changing the environment afterwards) or adding a dummy environment on the client in C:\ProgramData\PuppetLabs\code\environments.

Is this a bug?



edit retag flag offensive close merge delete


The "Error 400 on SERVER" bit indicates that the problem is on the master, not the agent. Does the development environment exist on the master?

csharpsteen gravatar imagecsharpsteen ( 2016-06-02 10:44:23 -0600 )edit

Yes, development does exist on the master. If I change the agent environment to production and do a puppet run, the mcollective files get installed and initialised. After this I can change the agent environment back to development and it will apply development correctly (without changes to master)

gerhard gravatar imagegerhard ( 2016-06-02 11:07:56 -0600 )edit