Bug 1747559 - Allow operation failure timeouts to be configured per operation in Pacemaker
Summary: Allow operation failure timeouts to be configured per operation in Pacemaker
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pacemaker
Version: 8.1
Hardware: All
OS: All
high
medium
Target Milestone: pre-dev-freeze
: 8.10
Assignee: Ken Gaillot
QA Contact: cluster-qe
Steven J. Levine
URL:
Whiteboard:
Depends On:
Blocks: 1747560
TreeView+ depends on / blocked
 
Reported: 2019-08-30 19:51 UTC by Ken Gaillot
Modified: 2023-08-10 15:40 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
The corresponding pcs functionality should be documented instead.
Clone Of:
: 1747560 (view as bug list)
Environment:
Last Closed: 2020-03-18 17:54:56 UTC
Type: Feature Request
Target Upstream Version: 2.1.7
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 4615921 0 None None None 2019-11-27 14:19:32 UTC

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


Note You need to log in before you can comment on or make changes to this bug.