Bug 1402152
| Summary: | RHEL 6 Pacemaker documentation steps for enabling pcsd are incorrect | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Sam Yangsao <syangsao> |
| Component: | doc-High_Availability_Add-On_Overview | Assignee: | Steven J. Levine <slevine> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | ecs-bugs |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.8 | CC: | cfeist, rhel-docs |
| Target Milestone: | rc | Keywords: | Documentation |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-03-22 18:41:34 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
Sam Yangsao
2016-12-06 22:37:11 UTC
OK, so from further testing, we do _need_ both services enabled. # chkconfig pcsd on # chkconfig pacemaker on As, without pcsd the node would not rejoin the cluster properly from verifying this. I would say, update the docs to make sure that 'pacemaker' service is turned by via chkconfig, even though we enable via the 'pcs cluster enable ...' command, we should also specify how to check that it gets started on reboot and how. This BZ is related: https://bugzilla.redhat.com/show_bug.cgi?id=1395639 Sam, You can see if pacemaker is enabled by running 'pcs status' on a running cluster and looking at the 'Daemon Status' section to verify that pacemaker is enabled. [root@host-600 lib]# pcs status .... snip .... Daemon Status: cman: active/disabled corosync: active/disabled pacemaker: active/enabled pcsd: active/disabled However, if the cluster is not running, you would need to do a 'chkconfig pacemaker list' to verify. I think we can have Steven update the docs to add both the 'pcs status' and 'chkconfig pacemaker list' checks to verify the cluster is enabled. Chris -- premature needinfo (that was meant for another bug). Clearing for the moment. Previously, the subsection on enabling cluster services was part of the "managing cluster nodes" section (as section 3.2.2). I have moved it to the end of the "cluster creation" section (as section 3.1.4) since it is part of the general creation process. I have also added the information about checking to be sure that clsuter services/pacemaker is enabled to the end of that chapter. The reason this was originally separated out from the general creation process is that not all sites would want to enable the cluster to start up on reboot -- if the cluster/node went down, you might want to be sure that node was fixed for sure before re-joining the cluster. There was some discussion about whether we should even recomment that users enable pcsd like this in the first place. But even separated out it does seem to belong in cluster creation. The section with the new information is here, Section 3.1.4: http://jenkinscat.gsslab.pnq.redhat.com:8080/job/doc-Red_Hat_Enterprise_Linux-6-Configuring_the_Red_Hat_High_Availability_Add-On_with_Pacemaker%20%28html-single%29/lastSuccessfulBuild/artifact/tmp/en-US/html-single/index.html#s2-enabledisableservices-HAAR Chris -- could you verify that information? thanks. Reviewed those sections, they look good to me. |