Issue #3149 has been updated by Hari Sekhon.

To clarify, I do use ntp, however, sometimes the time may get out of sync and 
ntpd may not correct it, so having an external check realign the time sorts it 
out and ntp can take over from there. Basically I've used -g with ntp and a 
trigger to the service to restart and step the time by however much it's out by 
(unlike the default which doesn't work if the time is too far out of sync).

I've disabled this behaviour, hoping ntpd will gradually adjust the time... and 
will see how it goes... but I still think this is a useful feature.
----------------------------------------
Feature #3149: notify => to trigger another resource only on failure of the 
current resource
http://projects.reductivelabs.com/issues/3149

Author: Hari Sekhon
Status: Unreviewed
Priority: Normal
Assigned to: 
Category: 
Target version: 
Affected version: 0.24.8
Keywords: 
Branch: 


I have a resource that I expect to run successfully all the time, and when it's 
not I want it to trigger the run of another resource that otherwise wouldn't 
run.

Basically inverting the success/failure criteria of a notify =>

What I used to do was have a time check exec, and negated the command, with a 
notify such that if the command actually failed (ie the time was out of sync by 
more than a few seconds) it would return success to puppet and that would 
trigger the notify => of another resource to fix the time.

However, once one starts doing reporting, this is not cool since it means that 
resource fails on every run on every machine from puppet's perspective and was 
really not a nice hack. It also litters the logs.


-- 
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.

Reply via email to