infochimps/cluster_chef — Issue #84: It looks like chef-client is setup to use runit, but not service?
Author: pcn
Created: 2011-12-16 20:48:38+00:00
State: open

Are you not having failures to complete the bootstrap script like this:

> ec2-50-17-110-208.compute-1.amazonaws.com ****ec2-50-17-110-208.compute-1.amazonaws.com **** Creating chef client script:ec2-50-17-110-208.compute-1.amazonaws.com ****ec2-50-17-110-208.compute-1.amazonaws.comec2-50-17-110-208.compute-1.amazonaws.com Fri Dec 16 20:08:30 UTC 2011ec2-50-17-110-208.compute-1.amazonaws.com
> ec2-50-17-110-208.compute-1.amazonaws.com ****ec2-50-17-110-208.compute-1.amazonaws.com **** Adding chef client runit scripts: ec2-50-17-110-208.compute-1.amazonaws.com ****
> ec2-50-17-110-208.compute-1.amazonaws.comec2-50-17-110-208.compute-1.amazonaws.com fail: chef-client: unable to change to service directory: file does not existec2-50-17-110-208.compute-1.amazonaws.com Chef bootstrap failed!

It seems like this needs to be run before service is invoked:

> update-service -a /etc/service chef-client

so that runit will manage chef-client as a service.

Or am I missing something here?