| Summary: | Support for sbd configuration is needed in pcs | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Tomas Jelinek <tojeline> |
| Component: | pcs | Assignee: | Ondrej Mular <omular> |
| Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.8 | CC: | cfeist, cluster-maint, cluster-qe, fdanapfe, idevat, jpokorny, lmiksik, mlisik, mnavrati, omular, rsteiger, tojeline |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | pcs-0.9.155-1.el6 | Doc Type: | Enhancement |
| Doc Text: |
Feature: Configuration of SBD fencing using pcs.
Reason: SBD cannot be configured using pcs.
Result: It is possible to configure SBD using pcs.
|
Story Points: | --- |
| Clone Of: | 1164402 | Environment: | |
| Last Closed: | 2017-03-21 11:04:28 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: | |
| Bug Depends On: | 1164402 | ||
| Bug Blocks: | |||
|
Comment 1
Ondrej Mular
2016-10-25 14:53:44 UTC
Before Fix: Sbd not supported. After Fix: [vm-rhel67-1 ~] $ rpm -q pcs pcs-0.9.155-1.el6.x86_64 [vm-rhel67-1 ~] $ pcs stonith sbd status SBD STATUS <node name>: <installed> | <enabled> | <running> vm-rhel67-1: YES | NO | NO vm-rhel67-2: YES | NO | NO [vm-rhel67-1 ~] $ pcs stonith sbd enable Running SBD pre-enabling checks... vm-rhel67-1: SBD pre-enabling checks done vm-rhel67-2: SBD pre-enabling checks done Distributing SBD config... vm-rhel67-1: SBD config saved vm-rhel67-2: SBD config saved Enabling SBD service... vm-rhel67-1: sbd enabled vm-rhel67-2: sbd enabled Warning: Cluster restart is required in order to apply these changes. [vm-rhel67-1 ~] $ pcs cluster stop --all && pcs cluster start --all vm-rhel67-2: Stopping Cluster (pacemaker)... vm-rhel67-1: Stopping Cluster (pacemaker)... vm-rhel67-2: Stopping Cluster (cman)... vm-rhel67-1: Stopping Cluster (cman)... vm-rhel67-1: Starting Cluster... vm-rhel67-2: Starting Cluster... [vm-rhel67-1 ~] $ pcs stonith sbd status SBD STATUS <node name>: <installed> | <enabled> | <running> vm-rhel67-1: YES | YES | YES vm-rhel67-2: YES | YES | YES [vm-rhel67-1 ~] $ pcs stonith sbd config SBD_WATCHDOG_TIMEOUT=5 SBD_STARTMODE=clean SBD_DELAY_START=no Watchdogs: vm-rhel67-1: /dev/watchdog vm-rhel67-2: /dev/watchdog [vm-rhel67-1 ~] $ pcs cluster stop --all vm-rhel67-2: Stopping Cluster (pacemaker)... vm-rhel67-1: Stopping Cluster (pacemaker)... vm-rhel67-2: Stopping Cluster (cman)... vm-rhel67-1: Stopping Cluster (cman)... [vm-rhel67-1 ~] $ pcs stonith sbd disable Checking corosync is not running on nodes... vm-rhel67-2: corosync is not running vm-rhel67-1: corosync is not running Disabling SBD service... vm-rhel67-1: sbd disabled vm-rhel67-2: sbd disabled 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. https://rhn.redhat.com/errata/RHBA-2017-0707.html |