Issue #6922 has been updated by eric sorenson.
Status changed from Investigating to Closed
This does not happen on current versions of puppet -- cowsay is not run.
<pre>
Debug: Exec[/Users/eric/Sandbox/true](provider=posix): Executing
'/Users/eric/Sandbox/true'
Debug: Executing '/Users/eric/Sandbox/true'
Notice: /Stage[main]//Exec[/Users/eric/Sandbox/true]/returns: executed
successfully
Info: /Stage[main]//Exec[/Users/eric/Sandbox/true]: Scheduling refresh of
Exec[/Users/eric/Sandbox/false]
Debug: /Stage[main]//Exec[/Users/eric/Sandbox/true]: The container Class[Main]
will propagate my refresh event
Debug: Exec[/Users/eric/Sandbox/false](provider=posix): Executing
'/Users/eric/Sandbox/false'
Debug: Executing '/Users/eric/Sandbox/false'
Error: /Stage[main]//Exec[/Users/eric/Sandbox/false]: Failed to call refresh:
/Users/eric/Sandbox/false returned 1 instead of one of [0]
Error: /Stage[main]//Exec[/Users/eric/Sandbox/false]: /Users/eric/Sandbox/false
returned 1 instead of one of [0]
Debug: Class[Main]: The container Stage[main] will propagate my refresh event
Debug: Finishing transaction 70265294028940
Debug: Storing state
Debug: Stored state in 0.00 seconds
Notice: Finished catalog run in 0.13 seconds
Debug: Using settings: adding file resource 'rrddir':
'File[/Users/eric/.puppet/var/rrd]{:path=>"/Users/eric/.puppet/var/rrd",
:mode=>"750", :ensure=>:directory, :loglevel=>:debug, :links=>:follow,
:backup=>false}'
Debug: Finishing transaction 70265294646280
Debug: Received report to process from cipater.local
Debug: Processing report from cipater.local with processor
Puppet::Reports::Store
[[email protected] ~/Sandbox]%
</pre>
----------------------------------------
Bug #6922: Failing resources in the middle of a chain should not notify
https://projects.puppetlabs.com/issues/6922#change-77637
Author: Doug Warner
Status: Closed
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.
