Issue #10465 has been updated by Charlie Sharpsteen. Keywords set to customer
---------------------------------------- Feature #10465: Provide a new "obsessive" mode which queries resources again after sync https://projects.puppetlabs.com/issues/10465#change-88565 * Author: Oliver Hookins * Status: Closed * Priority: Normal * Assignee: eric sorenson * Category: provider * Target version: * Affected Puppet version: * Keywords: customer * Branch: ---------------------------------------- Quite frequently there will be cases where the providers think they have done the right thing and report success even though the end result is not successful. This results in continual runs where there are successful changes but the overall outcome is the same - the system state is not what you want it to be. I would like for there to be a mode you can optionally enable that triggers a second query from the provider after the sync has occurred to see if the desired changes were actually done. If not, trigger a real error (which in fact is just reflecting more accurately the state of the machine than if we were to not perform this checking). In the case where Puppet is being used for larger orchestrated upgrades this is an essential component to figuring out if the desired changes were completed successfully and thus attention can be turned to the next machine(s) in the workflow. -- 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.
