RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
when yum install pacemaker is used, the pacemaker marks itself as enabled on boot (chkconfig --list pacemaker). This is not as expected and differs from other cluster daemons.

Version-Release number of selected component (if applicable):
pacemaker-1.1.10-6.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. yum install pacemaker
2. chkconfig --list pacemaker
3.

Actual results:
pacemaker       0:off   1:off   2:on    3:on    4:on    5:on    6:off


Expected results:
pacemaker       0:off   1:off   2:off    3:off    4:off    5:off    6:off


Additional info:

Looks like chkconfig is being a bit too smart for its own good.
I think we just need to apply:

diff --git a/mcp/pacemaker.in b/mcp/pacemaker.in
index c96f1d1..4c9ec6b 100644
--- a/mcp/pacemaker.in
+++ b/mcp/pacemaker.in
@@ -15,8 +15,6 @@
 # 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

Do we want this for 6.5?

we do want this for 6.5 :)

pacemaker-1.1.10-9.el6.x86_64:

Right after installation:
# chkconfig --list pacemaker
pacemaker      	0:off	1:off	2:off	3:off	4:off	5:off	6:off

Works as expected, marking as verified with pacemaker-1.1.10-9.el6.x86_64.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-1635.html