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.

This BZ is to track the updates to the SBD fencing article on the customer portal, as per this exchange:

From Ken Gaillot:

To summarize the support issue, this is where I think we should be:

* SBD is supported on RHEL 6.8 and later, and 7.1 and later.

* On RHEL 6, using SBD in clusters with an even number of nodes is not
supported, due to the lack of auto_tie_breaker.

* On RHEL 7, using SBD in clusters with an even number of nodes is
supported if "auto_tie_breaker: 1" is set in
/etc/corosync/corosync.conf. (Also, the article should mention doing
this step.)

* The other limitations in the article still apply: no Pacemaker Remote
(likely coming in 7.4, maybe 7.3.z if there is demand), no poison pill
(hopefully also 7.4), no software watchdogs (never).


Plus this, included here for completeness:

>>> https://access.redhat.com/solutions/2172091
>>>
>>> is the other reference we have for sbd support policies, which repeats
>>> the 'not supported in 6' line.  So obviously we missed something if that
>>> has changed.

The above should be updated; the equivalent notice for 6.8+ is:
https://access.redhat.com/errata/RHEA-2016:0985

To simplify finding it in the above exchange, this is the article to update:

https://access.redhat.com/articles/2212861

See also:

https://bugzilla.redhat.com/show_bug.cgi?id=1414053

Bug 1414053 - Clarify/update SBD doc re: support