cloud-init should restart chef, if it makes configuration changes and chef is already running.
Bug #1002412 reported by
Kiall Mac Innes
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| cloud-init |
Expired
|
Low
|
Avishai Ish-Shalom | ||
Bug Description
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.
| Changed in cloud-init: | |
| importance: | Undecided → Low |
| status: | New → Triaged |
| summary: |
- cloid-init should restart chef, if it makes configuration changes and + cloud-init should restart chef, if it makes configuration changes and chef is already running. |
| Changed in cloud-init: | |
| assignee: | nobody → Avishai Ish-Shalom (avishai-ish-shalom) |
| Changed in cloud-init: | |
| importance: | Low → Wishlist |
| importance: | Wishlist → Low |
Revision history for this message
| James Falcon (falcojr) wrote | #1 |
| Changed in cloud-init: | |
| status: | Triaged → Expired |
To post a comment you must log in.
Tracked in Github Issues as https:/