Bug 997346
| Summary: | pacemaker enables itself on boot during installation | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Jaroslav Kortus <jkortus> |
| Component: | pacemaker | Assignee: | Andrew Beekhof <abeekhof> |
| Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.5 | CC: | cluster-maint, dvossel |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | pacemaker-1.1.10-9.el6 | Doc Type: | Bug Fix |
| Doc Text: |
No description necessary
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-11-21 12:10:14 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Jaroslav Kortus
2013-08-15 08:28:04 UTC
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 |