Bug 1747559

Summary:	Allow operation failure timeouts to be configured per operation in Pacemaker
Product:	Red Hat Enterprise Linux 8	Reporter:	Ken Gaillot <kgaillot>
Component:	pacemaker	Assignee:	Ken Gaillot <kgaillot>
Status:	ASSIGNED ---	QA Contact:	cluster-qe <cluster-qe>
Severity:	medium	Docs Contact:	Steven J. Levine <slevine>
Priority:	high
Version:	8.1	CC:	cfeist, cluster-maint, knickel, lmiksik, phagara, pzimek, sbradley, slevine
Target Milestone:	pre-dev-freeze	Keywords:	FutureFeature, Reopened, Triaged
Target Release:	8.10
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:	The corresponding pcs functionality should be documented instead.	Story Points:	---
Clone Of:
Clones:	1747560 (view as bug list)		Environment:
Last Closed:	2020-03-18 17:54:56 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:	2.1.7
Embargoed:
Bug Depends On:
Bug Blocks:	1747560

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

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.

Comment 1 Patrik Hagara 2019-09-30 19:08:58 UTC

Setting QA CondNAK due to capacity constraints.

Comment 2 RHEL Program Management 2020-03-18 17:54:56 UTC

Quality Engineering Management has reviewed and declined this request. You may appeal this decision by reopening this request.

Comment 3 Patrik Hagara 2020-03-18 18:00:03 UTC

QA capacity CondNAK was valid for 8.2 only, reopening