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 1747563 - [RFE] start-failure-is-fatal as per-resource parameter instead of global property
Summary: [RFE] start-failure-is-fatal as per-resource parameter instead of global prop...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pcs
Version: 8.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: pre-dev-freeze
: ---
Assignee: Tomas Jelinek
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1328448
Blocks: 1679810
TreeView+ depends on / blocked
 
Reported: 2019-08-30 20:13 UTC by Ken Gaillot
Modified: 2021-09-04 07:26 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of: 1328448
Environment:
Last Closed: 2021-09-04 07:26:58 UTC
Type: Feature Request
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Ken Gaillot 2019-08-30 20:13:15 UTC 
+++ This bug was initially created as a clone of Bug #1328448 +++

Description of problem:


Currently the "start-failure-is-fatal" is cluster global property so it immediately affects all resources. Some customers would like to have possibility to set this property in per-resource fashion to achieve better granularity of resource behaviour.

Expected result:

Some resources could have the "start-failure-is-fatal" parameter enabled while others disabled.

--- Additional comment from Ken Gaillot on 2019-08-30 20:11:32 UTC ---

The current plan is to implement 2 new operation meta-attributes, failure-restart and failure-escalation, to replace start-failure-is-fatal, migration-threshold, and on-fail (which would still be supported for backward compatibility).

The first failure-restart=<N> failures would result in restart attempts, and if all failed, the response in failure-escalation would be taken (equivalent to the current on-fail values, except "restart", and adding "ban" to force the resource off its current node).

Thus a start action with failure-restart set to 0 would be equivalent to start-failure-is-fatal="true", and a start with action with failure-restart set to a positive number would be equivalent to start-failure-is-fatal="false" with migration_threshold set to that number.

pcs will need to accept the new options in pcs resource create and pcs op.
Comment 1 yuk 2020-04-17 14:43:49 UTC 
What's the meaning of this BZ?
It seems the same as https://bugzilla.redhat.com/show_bug.cgi?id=1328448
Comment 2 Ken Gaillot 2020-04-17 15:07:19 UTC 
(In reply to yuk from comment #1)
> What's the meaning of this BZ?
> It seems the same as https://bugzilla.redhat.com/show_bug.cgi?id=1328448

Bug 1328448 covers the pacemaker portion of the fix, and this bz covers the pcs interface.
Comment 8 RHEL Program Management 2021-03-02 07:31:00 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 13 Ken Gaillot 2021-06-09 14:51:45 UTC 
The pacemaker bz this depends on has been lowered in priority and will not make 8.5 and is not targeting any release at this point
Comment 17 RHEL Program Management 2021-09-04 07:26:58 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Note You need to log in before you can comment on or make changes to this bug.