Init script returns exit 0 for status when default has START=no

Bug #1267798 reported by Greg Sutcliffe
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
puppet (Ubuntu)
New
Medium
Unassigned

Bug Description

Currently, if one sets START=no in /etc/default/puppetmaster, the init script will exit with exit-code 0, regardless of whether the service is running or not. In the case where you have a puppet manifest like:

service { 'puppetmaster': ensure => stopped }

Puppet will try to stop the service on every agent run, because status is returning zero, so Puppet thinks it is running.

This issue was fixed upstream in this commit:

https://github.com/puppetlabs/puppet/commit/e48902a7d881e84861d366af5ff88fc0146037da

As it's a one-liner, could this be backported into the Ubuntu packages?

Thanks,
Greg

-- System Information:
Description: Ubuntu 12.04.3 LTS
Release: 12.04
Architecture: amd64 (x86_64)

puppetmaster:
  Installed: 2.7.11-1ubuntu2.7
  Candidate: 2.7.11-1ubuntu2.7
  Version table:
 *** 2.7.11-1ubuntu2.7 0
        500 http://nova.clouds.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages

Tags: precise
Greg Sutcliffe (ubun8u)
description: updated
description: updated
Revision history for this message
Robie Basak (racb) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

This sounds reasonable. Please see https://wiki.ubuntu.com/StableReleaseUpdates#Procedure for the process.

Mathew Hodson (mhodson)
tags: added: precise
Changed in puppet (Ubuntu):
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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