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.
Bug 1750427 - New sbd option 'SBD_TIMEOUT_ACTION' is not listed in pcs documentation
Summary: New sbd option 'SBD_TIMEOUT_ACTION' is not listed in pcs documentation
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pcs
Version: 8.1
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: 8.2
Assignee: Ondrej Mular
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 1803826
TreeView+ depends on / blocked
 
Reported: 2019-09-09 15:05 UTC by Nina Hostakova
Modified: 2023-06-04 09:14 UTC (History)
8 users (show)

Fixed In Version: pcs-0.10.4-5.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1803826 (view as bug list)
Environment:
Last Closed: 2020-04-28 15:27:56 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1664828 0 medium CLOSED add SBD_TIMEOUT_ACTION to allowed sbd options 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker RHELPLAN-29947 0 None None None 2023-06-04 09:14:55 UTC
Red Hat Product Errata RHEA-2020:1568 0 None None None 2020-04-28 15:28:14 UTC

Description Nina Hostakova 2019-09-09 15:05:06 UTC
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:

Comment 4 Miroslav Lisik 2019-11-29 08:53:47 UTC
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

Comment 12 Miroslav Lisik 2020-02-17 13:56:13 UTC
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.

Comment 16 errata-xmlrpc 2020-04-28 15:27:56 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-2020:1568


Note You need to log in before you can comment on or make changes to this bug.