Bug 1747560

Summary:	[RFE] Allow operation failure timeouts to be configured per operation in Pacemaker
Product:	Red Hat Enterprise Linux 8	Reporter:	Ken Gaillot <kgaillot>
Component:	pcs	Assignee:	Tomas Jelinek <tojeline>
Status:	CLOSED WONTFIX	QA Contact:	cluster-qe <cluster-qe>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.1	CC:	cfeist, cluster-maint, cluster-qe, idevat, mmazoure, omular, tojeline
Target Milestone:	pre-dev-freeze	Keywords:	FutureFeature, Reopened, Triaged
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:	1747559	Environment:
Last Closed:	2021-09-04 07:26:58 UTC	Type:	Feature Request
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1747559
Bug Blocks:

Description Ken Gaillot 2019-08-30 19:56:06 UTC

+++ This bug was initially created as a clone of Bug #1747559 +++

Description of problem: Currently, Pacemaker supports the "failure-timeout" resource meta-attribute, which will automatically clear a resource's failure history once it has no new failures in that much time. However, Pacemaker now tracks failure counts per operation, and is planned to offer more flexible failure handling, so it will be helpful to be able to set such timeouts individually per operation.


Actual results: Pacemaker supports setting failure-timeout as a resource meta-attribute.


Expected results: Pacemaker additionally supports setting the option as an operation property.


Additional info: The option might be renamed as part of this change.

pcs will need to accept the new option in operation options in pcs resource create and pcs op.

Comment 5 RHEL Program Management 2021-03-02 07:30:57 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 8 Ken Gaillot 2021-06-09 14:51:24 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 12 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.