On Tuesday, August 18, 2015 at 11:02:27 AM UTC-5, Christopher Wood wrote:
>
> Never used that, but it sounds like your instructions are using the Puppet
> 4 ("future") parser but your Learning VM or locally installed puppet is
> using the version 3 parser.
>
I'm not following why you say that. If the question were related to the
*parser
function* "each()" then it would make sense, but the question is actually
about a native Ruby function (or lack thereof) in an ERB.
The error message indicates that in the template context, the variable
designated by the error message has not been initialized (or has been
initialized to nil). That doesn't line up with the Puppet manifest
presented, but then again, neither does the line number reported in the
error message. I am therefore inclined to think that the manifest
presented is not the one that corresponds to the error message. Also,
though perhaps it's a simple typo, the apparent name of the manifest
presented is "init.p", not "init.pp". Puppet will not recognize the former.
So check your manifest. Ensure that it is named "init.pp", that it is
located in the correct directory, and that it in fact has the content
presented in the question. If the problem persists after confirming all
that then it may be that an older version of the compiled manifest is
cached. In that case, restarting the puppetmaster service will not fail to
clear the cache.
John
--
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/c203ca7b-0fee-4582-b989-e34b40f7a719%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
