[chef] Re: RE: Re: Re: Re: Re: Re: CHEF-3930: Run apt-get update automagically if apt-get install fails

Chronological Thread 
  • From: Greg Symons < >
  • To: < >
  • Subject: [chef] Re: RE: Re: Re: Re: Re: Re: CHEF-3930: Run apt-get update automagically if apt-get install fails
  • Date: Mon, 4 Mar 2013 17:05:25 -0600
  • Organization: DrillingInfo, Inc

I would argue this allows you to better specify the final, desired state of the system. As it stands now, if a chef-run fails, your system is left in an undefined state... it may be working, it may be working, but in a degraded state, or it may be completely failed. Nothing in your run_list specifies which of those states you are in after a failure. An on_failure resource allows you to fully specify the failure modes of your configuration. I think this is still declarative in that you're declaring changes to the configuration based on the status of other declared resources.


On 03/04/2013 01:33 PM, Kevin Keane Subscription wrote:
I didn't follow this discussion from the start, just saw this. Forgive me if I'm way 
off base here, but at first glance, this seems very wrong to me, the "it just 
feels strange" type of wrong.

Isn't the philosophy of Chef that resources should describe the final, desired, state of the 
system? This resource just feels "procedural" rather than "declarative".

Or am I way off on this?

-----Original Message-----
From: Adam Jacob 
Sent: Monday, March 4, 2013 9:13 AM

Subject: [chef] Re: Re: Re: Re: Re: CHEF-3930: Run apt-get update 
automagically if apt-get install fails

Why don't we make this a resource?

package "totally-sucks-devel"

on_failure "run apt-get update" do
   match /^package/
   notifies :run, "execute[apt-get-update]"

Where match is a regular expression that looks for names of resources.


On 3/4/13 9:06 AM, "Bryan McLellan" 
< >

On Fri, Mar 1, 2013 at 11:21 PM, Jesse Campbell 
< >
What about extending the current handler approach? Add the ability to
catch  a failed resource (by name) and retry it, just like you can
with a  begin/rescue.
I like the concept of having an exception handler be tied to a resource
or provider, or at least be able to determine what resource or provider
caused the exception, do some bits and retry.


Archive powered by MHonArc 2.6.16.