Issue #10465 has been updated by Oliver Hookins.

Actually the main use case I had for it was already in my summary. When using 
Puppet as a deployment tool you really want to be 100% sure you have succeeded 
on the current machine before moving on to the next. If you accept the end 
status of a Puppet run as an indication of the success of all of the providers 
you can easily take down an entire cluster of machines serving an application 
simply because the init script of your application server incorrectly returned 
0 when it shouldn't have.

Doing some more obsessive checks gives any deployment system wrapping around 
Puppet a better view of what has actually been achieved on each system and 
opens up the possibility to stop a potentially devastating upgrade or 
deployment before it takes all the machines down.
----------------------------------------
Feature #10465: Provide a new "obsessive" mode which queries resources again 
after sync
https://projects.puppetlabs.com/issues/10465

Author: Oliver Hookins
Status: Needs More Information
Priority: Normal
Assignee: Oliver Hookins
Category: provider
Target version: 
Affected Puppet version: 
Keywords: 
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 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