Issue #9782 has been updated by Steven Seed.
I understand the reasoning behind the change to keep the behavior consistent with including undefined classes in manifests. My problem is being an "external' node classifier, I don't currently have a way to validate whether or not the class I'm specifying in the ENC is valid or not and as it happens, the data I'm referencing and using for class names comes from a database that has other uses besides for puppet. If I could get some suggestion on how to validate the existence of a class from my ENC then I could check them before adding them to a node. ---------------------------------------- Bug #9782: Puppet (err): Could not find class <foo> for <host> in 2.7.3 on undefined class https://projects.puppetlabs.com/issues/9782 Author: Steven Seed Status: Unreviewed Priority: Normal Assignee: Category: Target version: Affected Puppet version: 2.7.3 Keywords: undefined class find Branch: My ENC has always added some extra classes not defined in puppet (things that I might end up using later based on the host name, department, or other attributes associated with the host in my database). In 0.25.5 the undefined class was reported at (info), in 2.6.9 it was reported as (warning), but in 2.7.3 it's an (err) ? This now causes my catalog to stop processing. Why the change to error now? 2.6.9: Puppet (warning): Could not find class tech for mohogany.fas.fa.disney.com 2.7.3: Puppet (err): Could not find class tech for mohogany.fas.fa.disney.com on node mohogany.fas.fa.disney.com -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
