[chef] Re: Re: Chef Failure and Lost Notifications

Chronological Thread 
  • From: Akzhan Abdulin < >
  • To:
  • Subject: [chef] Re: Re: Chef Failure and Lost Notifications
  • Date: Sat, 7 Apr 2012 12:12:28 +0400

I vote for this. Sometimes it's required.

2012/4/7 Peter Struijk < "> >
This topic has come up here before. There's also a ticket http://tickets.opscode.com/browse/CHEF-1067

What we need is an option to force a notify or make it sticky, even when the chef run fails.

I have been seeing this problem in my cookbooks where a recipe updates some
config and attempts to restart a service by sending a 'delayed' notification to
the service resource but another cookbook/recipe later in the run list fails.
The restart notification is never executed and during the next chef run the
config is correct and so the service is never restarted and config is never

The simple solution to this is to always use the :immediately tag, but then you
may end up restarting your service several times during a chef run.

Another option is to create a node on that machine for each recipe that starts
a service, but this seems like an administration pain.

Any thoughts?

Archive powered by MHonArc 2.6.16.