I ran into this problem also.
Are you access the variable $xxx_yyy will full puppet path? IE
$classname::xxx_yyy
If not you need to pass the variable into the template like this.
content => epp('module/template.epp', { 'xxx_yyy' => "$xxx_yyy"}),
Hope This helps
On Wednesday, November 4,
No mcollective can be used in addition to using puppet. Not required.
On Monday, August 3, 2015 at 9:47:08 AM UTC-4, HDub wrote:
>
> Hi Folks,
>
> I'm trying to get my head around puppet & mcollective and had a question.
> Is mcollective a neccessary service when deploying Puppet?
>
> thanks
I think this is a documentation issue only.
Looking at this ticket
https://tickets.puppetlabs.com/browse/FACT-826
I see mention of a different fact directory. Once i copied my facts to that
new directory it picks them up.
On Thursday, June 25, 2015 at 10:01:44 AM UTC-4, math...@therussells.
I just upgraded to puppet4.2 aio on some machines to fix a bug we have been
having with puppet.
But this introduced a new problem. It seems like out custom facts are not
being loaded by puppet or facter.
We have 3 external facts manually set in files.
[root@x facts.d]# ll /etc/facter/f
