Bug 1664828

Summary: add SBD_TIMEOUT_ACTION to allowed sbd options
Product: Red Hat Enterprise Linux 8 Reporter: Miroslav Lisik <mlisik>
Component: pcsAssignee: Ondrej Mular <omular>
Status: CLOSED ERRATA QA Contact: cluster-qe <cluster-qe>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 8.0CC: cfeist, cluster-maint, fdinitto, idevat, kwenning, nhostako, oalbrigt, omular, tojeline
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pcs-0.10.1-6.el8 Doc Type: Bug Fix
Doc Text:
Cause: User wants to set SBD option SBD_TIMEOUT_ACTION. Consequence: Pcs prints will exit with error informing user about SBD_TIMEOUT_ACTION not being valid SBD option. Fix: Add SBD_TIMEOUT_ACTION as supported SBD option when enabling SBD. Result: User is able to set SBD_TIMEOUT_ACTION without using --force parameter.
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-05 20:39:38 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:
Bug Depends On: 1660147, 1682129    
Bug Blocks:    

Comment 9 Ondrej Mular 2019-05-02 12:02:37 UTC
After fix:
[root@rhel81-node1 ~]# rpm -q pcs
pcs-0.10.1-6.el8.x86_64

[root@rhel81-node1 ~]# pcs stonith sbd enable SBD_TIMEOUT_ACTION=off,flush
Running SBD pre-enabling checks...
rh81-1: SBD pre-enabling checks done
rh81-2: SBD pre-enabling checks done
Distributing SBD config...
rh81-1: SBD config saved
rh81-2: SBD config saved
Enabling SBD service...
rh81-1: sbd enabled
rh81-2: sbd enabled
Warning: Cluster restart is required in order to apply these changes.
[root@rhel81-node1 ~]# pcs stonith sbd config
SBD_DELAY_START=no
SBD_STARTMODE=always
SBD_TIMEOUT_ACTION=off,flush
SBD_WATCHDOG_TIMEOUT=5

Watchdogs:
  rh81-2: /dev/watchdog
  rh81-1: /dev/watchdog

Comment 13 errata-xmlrpc 2019-11-05 20:39:38 UTC
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://access.redhat.com/errata/RHEA-2019:3311