Issue #21022 has been reported by Robert Lacroix. ---------------------------------------- Feature #21022: Notifications should be durable https://projects.puppetlabs.com/issues/21022
* Author: Robert Lacroix * Status: Unreviewed * Priority: Normal * Assignee: * Category: * Target version: * Affected Puppet version: 3.2.1 * Keywords: * Branch: ---------------------------------------- If a puppet run is canceled, crashes or is otherwise interrupted, notifications are lost. This is particularly bad if you consider the following scenario: 1. Puppet updates a configuration file that notifies a service to restart 2. Puppet schedules the restart 3. Puppet run is canceled In this case the file is already updated but the service is not restarted yet. Assuming there is nothing else that notifies it, the service is never restarted and you end up being in an inconsistent state. Also subsequent puppet runs don't fix this inconsistency. In my opinion notifications should be persisted to disk until they were exercised. A subsequent puppet run should then re-schedule outstanding notifications from a canceled previous run. -- 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
