Hello, It seems the autoload feature chokes (at least) on definitions named common::some_definition, although it all works when putting import "common" somewhere upstream. Are there any other module names to avoid? Felix Schäfer --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Felix Schäfer wrote:> Hello, > > It seems the autoload feature chokes (at least) on definitions named > common::some_definition, although it all works when putting import > "common" somewhere upstream. Are there any other module names to avoid? >Platform, version, error message, logs? Regards James Turnbull -- Author of: * Pulling Strings with Puppet (http://www.amazon.com/gp/product/1590599780/) * Pro Nagios 2.0 (http://www.amazon.com/gp/product/1590596099/) * Hardening Linux (http://www.amazon.com/gp/product/1590594444/)
Hello, Sorry, I thought it was something "obvious" maybe caused by some other common class in puppet elsewhere. Anyway: Am 04.09.2008 um 00:31 schrieb James Turnbull:> Platform, version,architecture => i386 facterversion => 1.5.0 kernel => Linux kernelrelease => 2.6.22.18-0.2-default lsbdistdescription => openSUSE 10.3 (i586) puppetversion => 0.24.4 rubyversion => 1.8.6 All that in a Parallels virtual machine, but that shouldn''t change anything...> error message,And now, I''m a little baffled, because I just ran "puppetd --verbose -- test" to make sure it still fails, which it did, but as I rerun the command with an appended ">> error_message", it went through, and still goes through... Still, a copy of the error: """ err: Could not retrieve catalog: Could not find resource type common::add_template_to_homes at /etc/puppet/modules/subversion/ manifests/init.pp:14 on node server.cypres.test """ The corresponding bit in the manifest: """ Common::Add_template_to_homes { module => "subversion", } [snip] common::add_template_to_homes { ".subversion/servers": ; } """> logs?Nothing for puppetmaster, same thing as on the CL in the puppetd log. Anyway, in runs through now, which would indicate some not-reloaded- after-update file by the puppetmaster, but it still makes me wonder why yesterday it was dependent on the presence of import "common" in the nodes.pp. Felix Schäfer --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, Sep 3, 2008 at 10:41 PM, Felix Schäfer wrote:> Anyway, in runs through now, which would indicate some not-reloaded- > after-update file by the puppetmaster, but it still makes me wonder > why yesterday it was dependent on the presence of import "common" in > the nodes.pp.This happens when you have a syntax error in your manifests, but you should see that in your puppetmaster logs. It can be hard to tickle out from the flood of log information, but the best way to spot it is tail the logs while you manually restart puppetmaster. - --Paul -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: http://getfiregpg.org iEYEARECAAYFAkjAQZQACgkQX6ecHn3cW4lLFgCeM3WeKAF1qLGoVmWnTHTr1fyb QUsAniB2umYZbENWl++NGxy/Gi0RznVv =3p15 -----END PGP SIGNATURE----- --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---