Hi Felix, >>puppet master --configprint all Does show that environmentpath is set when placed in [master] section, except client cannot find is modules anymore. Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class vmware for <fqdn> on node <fqn> >>some configuration issue Aha, if you could dig this up, that would be nice. Stefan
On Friday, May 16, 2014 12:44:13 PM UTC+2, Felix.Frank wrote: > On 05/16/2014 11:20 AM, Stefan Heijmans wrote: > > - directory environments > > Documentation says; "Set environmentpath = $confdir/environments in the > > puppet master’s puppet.conf (in the [master] or [main] section)." > > Except environmentpath does not work in the [master] section, [main] > > section works fine > > Checked with; puppet config print and value is empty when specified in > > [master] section. > > Hmm, > > about this one - that doesn't look correct to me. > > To see config as loaded by a master process, try > > puppet master --configprint all > > The other issues look legitimate to me, although the dual loading of > ruby code reminds me of some configuration issue that we helped at least > one other user fix in the past... > > Thanks, > Felix > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/3d4bbba1-7852-40cd-89e1-09b5cd1cc07a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
