pacemaker init.d script lacks runlevel definition

Bug #1427408 reported by James Page
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pacemaker (Ubuntu)
Fix Released
High
James Page
Vivid
Fix Released
High
James Page

Bug Description

Version from trusty:

### BEGIN INIT INFO
# Provides: pacemaker
# Required-Start: $network corosync
# Should-Start: $syslog
# Required-Stop: $network corosync
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Starts and stops Pacemaker Cluster Manager.
# Description: Starts and stops Pacemaker Cluster Manager.
### END INIT INFO

version in vivid:

### BEGIN INIT INFO
# Provides: pacemaker
# Required-Start: $network corosync
# Should-Start: $syslog
# Required-Stop: $network corosync
# Default-Start:
# Default-Stop:
# Short-Description: Starts and stops Pacemaker Cluster Manager.
# Description: Starts and stops Pacemaker Cluster Manager.
### END INIT INFO

This causes update-rc.d to not enable pacemaker in the right runlevels.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: pacemaker 1.1.11-1ubuntu2
ProcVersionSignature: User Name 3.19.0-7.7-generic 3.19.0
Uname: Linux 3.19.0-7-generic x86_64
ApportVersion: 2.16.2-0ubuntu1
Architecture: amd64
Date: Mon Mar 2 22:14:08 2015
Ec2AMI: ami-000001cc
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.small.osci
Ec2Kernel: aki-00000002
Ec2Ramdisk: ari-00000002
SourcePackage: pacemaker
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
James Page (james-page) wrote :
Revision history for this message
James Page (james-page) wrote :
Revision history for this message
James Page (james-page) wrote :

Pull request re-enabling runlevel config:

https://github.com/ClusterLabs/pacemaker/pull/656

I'll upload this as a patch to the 1.1.12 release if/when the release team approve.

Changed in pacemaker (Ubuntu):
status: New → Triaged
importance: Undecided → High
assignee: nobody → James Page (james-page)
status: Triaged → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package pacemaker - 1.1.12-0ubuntu1

---------------
pacemaker (1.1.12-0ubuntu1) vivid; urgency=medium

  * New upstream release (LP: #1426761):
    - d/p/Fix-services-Remove-cancelled-recurring-ops-from-internal-lists.patch,
      d/p/Fix-services-Do-not-allow-duplicate-recurring-op-ent.patch,
      d/p/High-lrmd-Merge-duplicate-recurring-monitor-operatio.patch,
      d/p/Fix-lrmd-cancel-recurring-operations-before-stop-act.patch:
      Dropped, included upstream.
    - d/control,d/libcib{3,4}*: Transition libcib3 -> libcib4.
    - d/libcrmcluster4-dev: Add crm/compatibility.h to install.
    - d/control: Bump minimum corosync version to 2.3.0.
  * d/lib*.install: Use wildcard for so installation to make packaging
    a little less brittle.
  * d/pacemaker.install: Wildcard installs in /usr/share/pacemaker to make
    packaging a little less brittle.
  * d/watch: Update to use github for release tracking
  * d/rules: Re-enable upstart support.
  * d/p/fix-init-default-start-stop.patch: Add default runlevels to
    pacemaker init script to ensure that it can be enabled correctly
    (LP: #1427408).
 -- James Page <email address hidden> Wed, 11 Mar 2015 12:35:49 +0000

Changed in pacemaker (Ubuntu Vivid):
status: In Progress → Fix Released
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.