Issue #18701 has been reported by Chris Price.
----------------------------------------
Bug #18701: If a resource is triggered by a refresh, and it fails, puppet
doesn't treat it as a failure
https://projects.puppetlabs.com/issues/18701
Author: Chris Price
Status: Unreviewed
Priority: Normal
Assignee:
Category:
Target version:
Affected Puppet version: 3.0.2
Keywords:
Branch:
This may be a dupe of #9237.
I have a module (puppetlabs/postgresql) that has some resources that are only
triggered via a refresh notification. In my case the resource is a custom ruby
type, but I stole some of its 'refreshonly' implementation from the Exec type,
so this may be simply a problem with the exec type rather than a more general
puppet problem. Here's an example that shows the problem using exec:
cprice@localhost ~/work/scratch $ puppet --version
3.0.2-rc2
cprice@localhost ~/work/scratch $ cat foo.pp
notify { "hi": } ~>
exec { "/bin/this_command_does_not_exist":
refreshonly => true,
}
cprice@localhost ~/work/scratch $ puppet apply ./foo.pp
No LSB modules are available.
No LSB modules are available.
Notice: hi
Notice: /Stage[main]//Notify[hi]/message: defined 'message' as 'hi'
Error: /Stage[main]//Exec[/bin/this_command_does_not_exist]: Failed to call
refresh: Could not find command '/bin/this_command_does_not_exist'
Error: /Stage[main]//Exec[/bin/this_command_does_not_exist]: Could not find
command '/bin/this_command_does_not_exist'
Notice: Finished catalog run in 0.18 seconds
cprice@localhost ~/work/scratch $ echo $?
0
cprice@localhost ~/work/scratch $
This has apparently been masking a legitimate bug in my module for several
months now.
--
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.
