On Wed, Nov 28, 2012 at 10:55 AM, John Lamb <lam...@wfu.edu> wrote: > I am also seeing this bug on one of my nodes (worryingly, the puppet master > itself!) The relevant output of puppet agent -t --debug --trace --verbose > matches what Fabrice and Lee have also reported:
OK, there's definitely a bug somewhere... I'm going to work on reproducing this issue tomorrow. Before then, could anyone affected by this "allocator undefined for Proc" error please let me know what exact versions of the operating system, Ruby, and Puppet they're running? If possible, if you could just privately email me the output of facter from an affected Puppet master that would be greatly helpful in reproducing this issue. Finally, could you please send me (privately) a copy and paste of all exported resources in your manifests? You can probably find them easiest with a recursive grep against "@@". This will help me populate the storedconfigs database so I can reproduce this issue. Thanks, -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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
