[chef] Re: Change restart/reload trigger order?

[Vincent Jorgensen < >]

I meant to say that keepalived and haproxy are restarting out of order.  Regardless, the problem is thus: keepalived gets a new configuration, which includes a new virtual ipaddress. haproxy gets the same ip address to add to it's frontend listening directive. But when haproxy restarts first, the ip address interface doesn't exist yet, so restart fails, which kills haproxy and all its running proxies. The first time I configure a new virtual ip, I have to manually restart keepalived so that haproxy can be properly restarted.

--------------------------------

Vincent Jorgensen

Operations Engineer @ Incentive Networks

650.226.4917 PDT (GMT-0700)

On Oct 5, 2012, at 11:22 AM, Ranjib Dey wrote:

by default the restarts are delayed until notified resource execution happens (as specied in the recipe, run list), unless you specify :immediately.  Can you share the specific example?

On Fri, Oct 5, 2012 at 11:49 PM, Vincent Jorgensen < " target="_blank"> > wrote:

Hi all!

Is there a clever way to enforce the order in which service restarts get triggered on a chef-client run? Basically, I need keepalived to trigger (and complete) first before httpd reloads or restarts. Right now I have to do the restarts by hand. Any ideas would be greatly appreciated.  Thanks!

--------------------------------

Vincent Jorgensen

Operations Engineer @ Incentive Networks