Re: [Puppet Users] Invalid resource type anchor.

4,498 views
Skip to first unread message

Jeff McCune

unread,
Oct 8, 2012, 4:14:26 PM10/8/12
to puppet...@googlegroups.com
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

Fran Rodríguez

unread,
Oct 9, 2012, 5:24:53 AM10/9/12
to puppet...@googlegroups.com
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. 

Hugh Cole-Baker

unread,
Oct 9, 2012, 6:20:33 AM10/9/12
to puppet...@googlegroups.com
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 type, is not being recognize. 


I had the same problem, caused by the puppetlabs-stdlib Ruby libraries not being available to the puppet master when it was parsing and compiling the manifests. It's related to bug http://projects.puppetlabs.com/issues/13858 as far as I can tell. The solution was to run puppet agent on the master itself, with pluginsync enabled, such that the required plugins from the puppetlabs-stdlib module get "synced" onto the master.

Fran Rodríguez

unread,
Oct 9, 2012, 11:01:55 AM10/9/12
to puppet...@googlegroups.com
Thanks Hugh, you are right!! Now it works.

banjer

unread,
Jul 9, 2013, 10:52:26 AM7/9/13
to puppet...@googlegroups.com
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 28, 2013 5:27:04 PM UTC-5, Ryan Trinder wrote:
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

jcbollinger

unread,
Jul 10, 2013, 8:46:55 AM7/10/13
to puppet...@googlegroups.com


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'm running puppet 3.x and had upgraded from 2.7.


No, it is not supposed to be installed by default.  It is not part of the core product.


John
 

Kevin D

unread,
Jul 10, 2013, 9:24:12 AM7/10/13
to puppet...@googlegroups.com
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 to be in that dir (having std lib in /etc/puppet/modules wouldn't be sufficient).
Reply all
Reply to author
Forward
0 new messages