Issue #6922 has been updated by Doug Warner.
I'm not running 2.6 currently, so I'd have to set up a new environment to test this. ---------------------------------------- Bug #6922: Failing resources in the middle of a chain should not notify https://projects.puppetlabs.com/issues/6922 Author: Doug Warner Status: Investigating Priority: Normal Assignee: Category: Target version: Affected Puppet version: 0.25.5 Keywords: Branch: Similar to bug#5670, I'm seeing failing resources still issue their refresh to other resources. We seem to be hitting this when we have something like Res[a] notify Res[b] (which fails) which notifies Res[c] (and still runs). An expanded test case from bug#5670: exec { "/bin/true": notify => Exec["/bin/false"], } exec { "/bin/false": refreshonly => true, notify => Exec["meh"], } exec { "meh": command => "/usr/bin/cowsay 'fail :('", refreshonly => true, logoutput => true } The Exec["meh"] resource will still be executed even though Exec["/bin/false"] fails. It appears to be triggered from the initial Exec["/bin/true"] that succeeds. -- 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.
