Issue #2339 has been updated by Luke Kanies. Status changed from Needs design decision to Rejected
FTR, we explicitly added this behaviour when we created external node support. I think this behaviour makes sense because it allows a cleaner separation between external nodes and Puppet -- they don't each have to have the same definition of 'class'. That is, Puppet requires that classes have code attached, but it's reasonable for external nodes not to require that. For now, I'm going to reject this, but that's not a hard rejection -- if you feel strongly about it, open a thread on the dev list with your justification. ---------------------------------------- Bug #2339: puppet doesn't fails if a class defined in external nodes doesn't exists http://projects.reductivelabs.com/issues/2339 Author: Benoit Decherf Status: Rejected Priority: Normal Assigned to: Luke Kanies Category: plumbing Target version: Complexity: Unknown Affected version: 0.24.7 Keywords: In the external node, I have: classes: - toto And toto doesn't exists. When I execute puppet, I juste have a message that the classe doesn't exists: info: Could not find class toto for rogue.xxx.com If I use puppet without external node (include "toto" in the node): Could not find class toto at /opt/puppet/manifests/site.pp:11 on node rogue.xxx.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://reductivelabs.com/redmine/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 -~----------~----~----~----~------~----~------~--~---
