Hah, indeed. 3.5.0 has introduced some fun changes ;-) Thanks for your help!
On Tuesday, May 20, 2014 4:42:04 PM UTC-4, Christopher Wood wrote:
>
> Sorry, I've stayed at 3.4.3 so that the exciting things can happen to
> other people for a while.
>
> Were I debugging this, I'd check my data to ma
Sorry, I've stayed at 3.4.3 so that the exciting things can happen to other
people for a while.
Were I debugging this, I'd check my data to make sure that everything was the
same as from 3.4.2 and then try to reproduce using the simplest pp file I could
(then maybe file a bug).
On Tue, May 20,
Thanks for the tip, worked like a charm. Turns out I had some variables
with an uppercase first letter.
Got past that, but now I'm also dealing with something else unexpected.
Info: Retrieving pluginfacts
Info: Retrieving plugin
Error: Could not retrieve catalog from remote server: Error 400 on
If you run your puppetmaster in the foreground with debug enabled it might tell
you more. (You'll have to stop the usual daemon first, and run it as the usual
user not root.)
puppet master --debug --no-daemonize 2>&1 | tee /var/tmp/pm1.log
Also use --config in there if you need it, of course.
Hey team,
Testing the waters with the new Future Parser functionality.
I've enabled it in [main] and [master] with parser = future, in my
puppet.conf, and am running puppet v3.5.1. Earlier versions of puppet
(namely, 3.4.2) worked fine with this setting enabled and the exact same
modules. I k
