Nailed it. Accidentally had the include outside the class at "top- level". That's a scary uhum feature. Might need to look into integrating some test code that looks for top-level includes within the modules dir and warns. Thanks John!
-Ryan On Mar 29, 5:42 am, jcbollinger <john.bollin...@stjude.org> wrote: > On Mar 28, 3:00 pm, Ryan Bowlby <rbowlb...@gmail.com> wrote: > > > I'm having an issue where every single puppet node included our yum > > class as part of the catalog. In all instances the nodes node > > definition was empty. Has anyone experienced something like this > > before? Is the yum class colliding with an internal class? > > > We do not define a node default or use any node regex that would have > > caused this. No other rogue classes are being included except the yum > > class. > > My first guess would be that you declare your yum class at top level > (== outside any node definition or other class) somewhere in one of > the manifests that all the affected nodes use. Top-level declarations > apply to all nodes, and they can be in any manifest file. > > John -- 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.
