cloud-init

Check puppet run state before starting/restarting

Bug #1090218 reported by Craig Tracey
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
cloud-init
Invalid
Medium
Craig Tracey

Bug Description

Right now the puppet module will call 'service puppet start' at the end of every run. Depending on puppet's state when we have completed execution, cloud-init should either start it if it is not running or restart it if the configuration has changed and it is already running.

Related branches

lp:~craigtracey/cloud-init/puppet-service-restart
Scott Moser: Needs Fixing
Diff: 36 lines (+16/-1)
1 file modified
cloudinit/config/cc_puppet.py (+16/-1)
Craig Tracey (craigtracey)
Changed in cloud-init:
assignee: nobody → Craig Tracey (craigtracey)
Scott Moser (smoser)
Changed in cloud-init:
importance: Undecided → Medium
Scott Moser (smoser)
Changed in cloud-init:
status: New → Triaged
Revision history for this message
Graham Leggett (minfrin-y) wrote :

Seems https://bugs.launchpad.net/cloud-init/+bug/1355909 describes breakage that might be fixed by this patch.

Revision history for this message
James Falcon (falcojr) wrote :

Puppet module has been modified many times since the creation of this bug. Current module behavior is to run the module once per instance with config options to install service and/or start at end of run. Because of this, I'm closing this as invalid.

Changed in cloud-init:
status: Triaged → Invalid
Revision history for this message
James Falcon (falcojr) wrote :

Tracked in Github Issues as https://github.com/canonical/cloud-init/issues/2338

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.