On Sun, Nov 27, 2011 at 2:48 PM, Jo Rhett <jrh...@netconsonance.com> wrote:
> On Sat, Nov 26, 2011 at 7:25 PM, Jo Rhett <jrh...@netconsonance.com>wrote: > >> On Nov 25, 2011, at 11:59 AM, Peter Berghold wrote: >> >> err: Could not retrieve catalog from remote server: Error 400 on SERVER: >> Could not find class adminscripts::getvpsnodes for >> slccrepos0.slc.sharkrivertech.com at >> /etc/puppet/manifests/nodes/slccrepos0.pp:4 on node >> slccrepos0.slc.sharkrivertech.com >> warning: Not using cache on failed catalog >> err: Could not retrieve catalog; skipping run >> >> I know it has to be me... what am I missing here? >> >> >> It doesn't mean it's not there -- seems to often mean there's a problem >> in the module. I've come to learn that this error means "there is something >> wrong when parsing your module" and you have to go look blindly to figure >> it out. This is somewhere that puppetlabs could improve things greatly. >> > > On Nov 27, 2011, at 7:28 AM, Nigel Kersten wrote: > > If there's a parse error in the manifests, that will be shown, but only > each time Puppet re-parses them. > > ... > > If you're definitely seeing modules fail to parse, with no errors being > thrown, and then the class subsequently can't be found, please bug report, > as that's definitely a bug. You shouldn't be completely "blind" here. > > > Assuming that what you say above is right, I would suggest that showing > the error only once is only useful for single-digit puppet installations. > The problem here is that I have 500+ nodes. So let's say I'm adjusting a > module and testing the effect with "--test". I adjust the module code, > then I run "puppet agent --test" on the node which should be affected, and > I don't see the error message related to my changes -- only this complaint > that the module isn't found. Perhaps some other node hit the server first > (with about 10 nodes connected at any time, this is fairly likely) and you > reported the error to it -- but how can I see this? Should I stumble around > on 500 nodes and try to figure out which one contains the error? > No, you should see it in the puppet master logs. Does it not show up there? You certainly shouldn't be having to hunt around on nodes to discover errors like this. -- Nigel Kersten Product Manager, Puppet Labs -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
