Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
pcs has added 'SBD_TIMEOUT_ACTION' to supported options. However it is not documented neither in help nor in pcs man page
Version-Release number of selected component (if applicable):
pcs-0.10.2-4.el8.x86_64
How reproducible:
always
Steps to Reproduce:
1. check pcs help
[root@virt-030 ~]# pcs stonith sbd --help | grep 'SBD options' -A5 -B5
Usage: pcs stonith sbd...
sbd enable [watchdog=<path>[@<node>]]... [device=<path>[@<node>]]...
[<SBD_OPTION>=<value>]... [--no-watchdog-validation]
Enable SBD in cluster. Default path for watchdog device is
/dev/watchdog. Allowed SBD options: SBD_WATCHDOG_TIMEOUT (default: 5),
SBD_DELAY_START (default: no) and SBD_STARTMODE (default: always). It is
possible to specify up to 3 devices per node. If
--no-watchdog-validation is specified, validation of watchdogs will be
skipped.
2. check man pcs
[root@virt-030 ~]# man pcs | grep 'SBD options' -A1 -B1
sbd enable [watchdog=<path>[@<node>]]... [device=<path>[@<node>]]... [<SBD_OPTION>=<value>]... [--no-watchdog-validation]
Enable SBD in cluster. Default path for watchdog device is /dev/watchdog. Allowed SBD options: SBD_WATCHDOG_TIMEOUT (default: 5), SBD_DELAY_START (default: no) and SBD_STARTMODE (default:
always). It is possible to specify up to 3 devices per node. If --no-watchdog-validation is specified, validation of watchdogs will be skipped.
Actual results:
'SBD_TIMEOUT_ACTION' is not mentioned in allowed SBD options
Expected results:
The option should be documented including the values that can be set
Additional info:
Test:
[root@r8-node-03 pcs]# rpm -q pcs
pcs-0.10.4-1.el8.x86_64
[root@r8-node-03 pcs]# pcs stonith sbd enable --help | grep -A 3 "SBD options"
/dev/watchdog. Allowed SBD options: SBD_WATCHDOG_TIMEOUT (default: 5),
SBD_DELAY_START (default: no), SBD_STARTMODE (default: always) and
SBD_TIMEOUT_ACTION. It is possible to specify up to 3 devices per node.
If --no-watchdog-validation is specified, validation of watchdogs will
Test:
[root@r8-node-01 ~]# rpm -q pcs
pcs-0.10.4-5.el8.x86_64
[root@r8-node-01 ~]# MAXWIDTH=80 man pcs | grep -C 1 sbd\(8\)
Enable SBD in cluster. Default path for watchdog device is /dev/watchdog. Allowed SBD options: SBD_WATCHDOG_TIMEOUT (default: 5), SBD_DELAY_START (default: no), SBD_STARTMODE (default: always) and SBD_TIMEOUT_ACTION. SBD options are documented in
sbd(8) man page. It is possible to specify up to 3 devices per node. If --no-watchdog-validation is specified, validation of watchdogs will be skipped.
--
sbd device message <device-path> <node> <message-type>
Manually set a message of the specified type on the device for the node. Possible message types (they are documented in sbd(8) man page): test, reset, off, crashdump, exit, clear
--
boothd(8), sbd(8)
[root@r8-node-01 ~]# pcs stonith sbd enable --help | grep -C 1 sbd\(8\)
SBD_DELAY_START (default: no), SBD_STARTMODE (default: always) and
SBD_TIMEOUT_ACTION. SBD options are documented in sbd(8) man page. It
is possible to specify up to 3 devices per node.
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-2020:1568
Description of problem: pcs has added 'SBD_TIMEOUT_ACTION' to supported options. However it is not documented neither in help nor in pcs man page Version-Release number of selected component (if applicable): pcs-0.10.2-4.el8.x86_64 How reproducible: always Steps to Reproduce: 1. check pcs help [root@virt-030 ~]# pcs stonith sbd --help | grep 'SBD options' -A5 -B5 Usage: pcs stonith sbd... sbd enable [watchdog=<path>[@<node>]]... [device=<path>[@<node>]]... [<SBD_OPTION>=<value>]... [--no-watchdog-validation] Enable SBD in cluster. Default path for watchdog device is /dev/watchdog. Allowed SBD options: SBD_WATCHDOG_TIMEOUT (default: 5), SBD_DELAY_START (default: no) and SBD_STARTMODE (default: always). It is possible to specify up to 3 devices per node. If --no-watchdog-validation is specified, validation of watchdogs will be skipped. 2. check man pcs [root@virt-030 ~]# man pcs | grep 'SBD options' -A1 -B1 sbd enable [watchdog=<path>[@<node>]]... [device=<path>[@<node>]]... [<SBD_OPTION>=<value>]... [--no-watchdog-validation] Enable SBD in cluster. Default path for watchdog device is /dev/watchdog. Allowed SBD options: SBD_WATCHDOG_TIMEOUT (default: 5), SBD_DELAY_START (default: no) and SBD_STARTMODE (default: always). It is possible to specify up to 3 devices per node. If --no-watchdog-validation is specified, validation of watchdogs will be skipped. Actual results: 'SBD_TIMEOUT_ACTION' is not mentioned in allowed SBD options Expected results: The option should be documented including the values that can be set Additional info: