Issue #3382 has been updated by Alan Harder. Affected version changed from 0.25.4 to 2.6.0rc4
Glad you tracked it down! Hope it can be fixed someday, so we can stop using our "empty_class" define to add a notify resource in such cases. I'm updating the affected version above to 2.6.0rc4. ---------------------------------------- Bug #3382: Class require chain thru class with no resources http://projects.puppetlabs.com/issues/3382 Author: Alan Harder Status: Accepted Priority: Normal Assigned to: Brice Figureau Category: functions Target version: Affected version: 2.6.0rc4 Keywords: require Branch: This may be working as designed, but wanted to file an issue to make sure. Consider this test case: <pre> class foo { notify { 'foo': } class bar { require foo # notify { 'bar': } } } class baz { require foo::bar notify { 'baz': } } node default { include baz } </pre> When notify 'bar' is uncommented, this works as expected.. the notify messages always appear in order: foo, bar, baz. However, with notify 'bar' commented the order is sometimes foo,baz and sometimes baz,foo. It seems that some resource must be in the foo::bar class to enforce that foo is evaluated before baz. Is this expected that a class level "require" chain only works when each link in the chain has at least one resource? I use a setup like this sometimes where a subclass sets some variables and then requires the outer class, so it has no resources of its own. If you have another recommended way to do this, let me know :-) I guess I could do "require foo::bar, foo" but that's less intuitive usage. Thanks. -- 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.
