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.

Document URL: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/High_Availability_Add-On_Reference/ch-clusteropts-HAAR.html

Section Number and Name: 10.1. Summary of Cluster Properties and Options

Describe the issue: The definition of start-failure-is-fatal is unclear about what "fatal" means.

Suggestions for improvement: Indicates whether a failure to start a resource on a particular node prevents further start attempts on that node. If FALSE, the cluster will decide whether to try starting on the same node again based on the resource's current failure count and migration-threshold.

Additional information: Also, section "7.2. Moving Resources Due to Failure" says: "Start failures cause the failcount to be set to INFINITY and thus always cause the resource to move immediately." That should begin, "If the cluster property start-failure-is-fatal is set to true (which is the default), ...".

When this is updated and reviewed, we need to make the same changes to the RHEL 6 Pacemaker document as well. (I'll either clone this BZ or add this as a topic to the more general RHEL 6.8 BZ on general backport of RHEL 7 updates to RHEL 6.)

I've made this changes to the draft of the document. When I next build this document I will send them for review, after which I will make the same changes to the RHEL 6 document.

These changes as noted are in the draft of the document for both RHEL 7 and RHEL 6.8.