cloud-init should restart chef, if it makes configuration changes and chef is already running.

This bug was originally filed in Launchpad as [LP: #1002412](https://bugs.launchpad.net/cloud-init/+bug/1002412)

Launchpad details

affected_projects = []

assignee = avishai-ish-shalom

assignee_name = Avishai Ish-Shalom

date_closed = None

date_created = 2012-05-21T18:17:40.874971+00:00

date_fix_committed = None

date_fix_released = None

id = 1002412

importance = low

is_complete = False

lp_url = https://bugs.launchpad.net/cloud-init/+bug/1002412

milestone = None

owner = kiall

owner_name = Kiall Mac Innes

private = False

status = triaged

submitter = kiall

submitter_name = Kiall Mac Innes

tags = []

duplicates = []

_Launchpad user **Kiall Mac Innes(kiall)** wrote on 2012-05-21T18:17:40.874971+00:00_

We have some image that has chef pre-installed, but not pre-configured. Cloud-init correctly configures Chef, but chef does not pick up the settings..

Ideally, cc_chef would check if the `chef-client` service is already installed+running, and if so issue a restart.