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 is not present or
something like that, the dependencies of the modulo are installed, stdlib
and i tried to use it without any declaration on my own apt class, but im
still getting this error. Someone has any idea what is happening?¿ Thanks.
My class:
class apt-basic {
include apt::backports
class { ''apt'': }
class { ''apt::backports'':
release => ''squeeze'',
}
apt::source {
''security.debian.org.deb'':
location => ''http://security.debian.org/'',
repos => ''main contrib non-free'',
include_src => true,
release => ''squeeze/updates'',
}
apt::source {
''updates.debian.org.deb'':
location => ''http://ftp.de.debian.org/debian'',
repos => ''main contrib non-free'',
include_src => true,
release => ''squeeze-updates'',
}
apt::source {
''squeeze.ftp.fr.debian.org.deb'':
location => ''http://ftp.de.debian.org/debian'',
repos => ''main contrib non-free'',
include_src => true,
release => ''squeeze'',
}
}
And this is what i get on puppetmaster log, the line what is talking is the
next on init.pp:
anchor { ''apt::update'':
require => Class[''apt::update''],
}
debug: importing
''/etc/puppet/environments/development/modules/apt/manifests/init.pp''
in
environment development
debug: importing
''/etc/puppet/environments/development/modules/apt/manifests/backports.pp''
in environment development
debug: Automatically imported apt::backports from apt/backports into
development
debug: importing
''/etc/puppet/environments/development/modules/apt/manifests/params.pp''
in
environment development
debug: Automatically imported apt::params from apt/params into development
debug: importing
''/etc/puppet/environments/development/modules/apt/manifests/source.pp''
in
environment development
debug: Automatically imported apt::source from apt/source into development
debug: importing
''/etc/puppet/environments/development/modules/apt/manifests/update.pp''
in
environment development
debug: Automatically imported apt::update from apt/update into development
err: Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid
resource type anchor at
/etc/puppet/environments/development/modules/apt/manifests/init.pp:113 on
node
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/kgyf1YbtRkoJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
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@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
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, Jeff McCune wrote:> > 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 view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/42ZExBWww2wJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
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 view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/NnZGhz0U58YJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
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/13858as 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 view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/S8PlYcE24TAJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
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 post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
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+unsubscribe@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.
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 -- 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+unsubscribe@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.
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). On Tuesday, July 9, 2013 8:52:26 AM UTC-6, 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. > > 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+unsubscribe@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.