On 08.03.2013 09:33, christian.le.fl...@gmail.com wrote:
Hi, I’ve got no idea if this is a bug or some kind of misuse/misconfiguration. Hope somebody can help. Thanks!If I change a file in a module or manifest directory this /often/ results in errors, mostly of the following kinds * Could not find class for on node * Cannot find definition Class on node These errors occur when puppet modules/manifests are changed – but it happens only once. If it happens affected puppet agents will use their cached catalog once. *The next time these agents request a catalog it is compiled flawlessly and everything will work like a charm* – all errors are gone. Problem is we have agents with large catalogs. Their catalog runs can take up to over a minute and so the time it takes for a change to be applied will then be doubled to take up to 2 or even 3 minutes. Usually changes of modules/manifests are performed by “git pull”. But it’s easy to reproduce these error messages by simple “touch” operations. Here are some interesting log observations and their [commonness]. Yes AFAICS they always appear in triplets. It rarely happens that there are no problems at all after a modification.
Hi, I've reported a similar issue recently here: https://projects.puppetlabs.com/issues/19638 I've tracked my problem to overshooting use of "import" calls in modules. You might want to check if you're hitting the same bug. Best Regards, David -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
