I also believe that stdlib needs to be in the same directory of the
referenced (or specified) module path. In other words, if moduleA is in
/etc/pupppet/modules, then stdlib needs to be in the same parent directory
as moduleA. Consequently, if moduleB is in /var/temp/puppet/modules, std
needs
On Tuesday, July 9, 2013 9:52:26 AM UTC-5, banjer wrote:
>
> I had to install the puppet stdlib module with:
>
> *puppet module install puppetlabs/stdlib*
>
>
> and that fixed the issue. It wasn't available in my /etc/puppet/modules.
> I'm not sure if its *supposed* to be installed by default.
I had to install the puppet stdlib module with:
*puppet module install puppetlabs/stdlib*
and that fixed the issue. It wasn't available in my /etc/puppet/modules.
I'm not sure if its *supposed* to be installed by default. I'm running
puppet 3.x and had upgraded from 2.7.
On Monday, January
I noticed that puppet modules installs modules in */etc/puppet/modules*,
which is different than where I keep my modules. I added* /etc/puppet/modules
*to the* modulepath *in puppet.conf, fixed the problem
On Tuesday, October 9, 2012 11:01:55 AM UTC-4, Fran Rodríguez wrote:
>
> Thanks Hugh, you
Thanks Hugh, you are right!! Now it works.
On Tuesday, October 9, 2012 12:20:33 PM UTC+2, Hugh Cole-Baker wrote:
>
> On Tuesday, October 9, 2012 10:24:53 AM UTC+1, Fran Rodríguez wrote:
>
>> Yes, it does. This occurs when change apt module for the puppetlabs-apt.
>> Maybe is a issue with environm
On Tuesday, October 9, 2012 10:24:53 AM UTC+1, Fran Rodríguez wrote:
> Yes, it does. This occurs when change apt module for the puppetlabs-apt.
> Maybe is a issue with environments, im trying to figure out what is
> happening, and like the log said the module stdlib which provide the anchor
> t
Yes, it does. This occurs when change apt module for the puppetlabs-apt.
Maybe is a issue with environments, im trying to figure out what is
happening, and like the log said the module stdlib which provide the anchor
type, is not being recognize.
On Monday, October 8, 2012 10:15:46 PM UTC+2, J
That's a strange issue. I wonder if it's caused by the class name
containing a hyphen?
Does this happen to be the puppetlabs-apt module?
-Jeff
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@g
Hi group, im updating some modules of puppet, and i found this issue or
error, that i cannot get resolved it. My puppetmaster is 2.7.1 and client
2.7.18. I used other modulo to prover apt configurations but i think this
is more completed.
I know that the error is something missing or my class
