Success! I've figured out what happened! It looks like not just custom functions disappeared, but also functions that are part of puppet disappeared (like split()). In fact, it looks like anything that was loaded into puppet via Puppet::Parser::Functions had disappeared (not knowing much about Puppet internals, I'm guessing that there's a table or hash that the functions are stored in, or they're added as methods).
One of the modules I use is ghoneycutt's puppet-xinetd module: https://github.com/ghoneycutt/puppet-xinetd . This module includes spec test files. Once I removed the spec directory and restarted the puppet master, all was well. I expect that the real issue here is that all of Puppet's internal functions got whacked because of bad tests in the spec direcotry in puppet-xinetd. The error messge, while technically true, didn't do much to point me in the right direction. Is there a way that Puppet can test whether or not expected functions are present, refuse to start if they are not, and log a more informative error? --dlloyd On Wed, Jul 18, 2012 at 4:17 PM, Dave Lloyd <d...@davelloyd.com> wrote: > Nan: > > Since my test module worked and copying and pasting would be at best > cumbersome, I've just created a github project with my module: > https://github.com/ibikestl/puppet-netif > > Examples should be in the tests. > > Thanks again for your help on this, > > --dlloyd > > > -- 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.
