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 > > On Tuesday, October 9, 2012 11:01:55 AM UTC-4, Fran RodrÃguez wrote: >> >> 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 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. >>> >> -- 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 puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
