1919910 – The fail counts cannot be reset after the failure-timeout until cluster-recheck-interval arrived

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 1919910 - The fail counts cannot be reset after the failure-timeout until cluster-recheck-interval arrived

Summary: The fail counts cannot be reset after the failure-timeout until cluster-reche...

Keywords:
Status:	CLOSED WONTFIX
Alias:	None
Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	pacemaker
Sub Component:
Version:	7.9
Hardware:	x86_64
OS:	Linux
Priority:	unspecified
Severity:	high
Target Milestone:	rc
Target Release:	---
Assignee:	Ken Gaillot
QA Contact:	cluster-qe@redhat.com
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2021-01-25 11:48 UTC by chengliu
Modified:	2022-08-17 16:57 UTC (History)
CC List:	2 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2021-01-25 15:29:23 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Bugzilla	1747553	0	high	CLOSED	Dynamically calculate Pacemaker's cluster recheck interval	2024-10-01 16:22:55 UTC
Red Hat Knowledge Base (Solution)	3599641	0	None	None	None	2022-08-17 16:57:38 UTC

Description chengliu 2021-01-25 11:48:27 UTC

Description of problem:

After failure-timeout reached, the fail count isn't cleared and resources did not move back to the original node according to the location restriction.
It is waiting for cluster-recheck-interval to expire.

Version-Release number of selected component (if applicable):

pacemaker-1.1.23-1.el7

How reproducible:

Steps to Reproduce:
1. 2 node cluster
2. Configure the resource with meta attributes "failure-timeout=120s migration-threshold=1"
3. Configure location constraints for resources

Actual results:

The resources move back to the original node after cluster-recheck-interval expired instead of checking the failure-timeout setting.
~~~
  Resource: Website (class=ocf provider=heartbeat type=apache)
   Attributes: configfile=/etc/httpd/conf/httpd.conf statusurl=http://127.0.0.1/server-status
   Meta Attrs: failure-timeout=120s migration-threshold=1   
   Operations: monitor interval=10s timeout=20s (Website-monitor-interval-10s)
               start interval=0s timeout=40s (Website-start-interval-0s)
               stop interval=0s timeout=60s (Website-stop-interval-0s)

Location Constraints:
  Resource: apachegroup
    Enabled on: host2.example.com (score:2000) (id:location-apachegroup-host2.example.com-2000)

# pcs property --all | grep recheck
 cluster-recheck-interval: 15min

[root@host2 ~]# date; pcs resource
Mon Jan 25 02:24:43 EST 2021
 Resource Group: apachegroup
     my_lvm	(ocf::heartbeat:LVM):	Started host2.example.com
     my_fs	(ocf::heartbeat:Filesystem):	Started host2.example.com
     VirtualIP	(ocf::heartbeat:IPaddr2):	Started host2.example.com
     Website	(ocf::heartbeat:apache):	Started host2.example.com

[root@host2 ~]# date && killall -9 httpd && sleep 30 && crm_resource --wait && pcs resource
Mon Jan 25 02:25:52 EST 2021
 Resource Group: apachegroup
     my_lvm	(ocf::heartbeat:LVM):	Started host1.example.com
     my_fs	(ocf::heartbeat:Filesystem):	Started host1.example.com
     VirtualIP	(ocf::heartbeat:IPaddr2):	Started host1.example.com
     Website	(ocf::heartbeat:apache):	Started host1.example.com

[root@host2 ~]# date; pcs resource
Mon Jan 25 02:28:12 EST 2021
 Resource Group: apachegroup
     my_lvm	(ocf::heartbeat:LVM):	Started host1.example.com
     my_fs	(ocf::heartbeat:Filesystem):	Started host1.example.com
     VirtualIP	(ocf::heartbeat:IPaddr2):	Started host1.example.com
     Website	(ocf::heartbeat:apache):	Started host1.example.com

[root@host2 ~]# pcs resource failcount show Website
Failcounts for resource 'Website'
  host2.example.com: 1

[root@host2 ~]# date;pcs resource failcount show Website;pcs resource
Mon Jan 25 02:42:56 EST 2021
No failcounts for resource 'Website'
 Resource Group: apachegroup
     my_lvm	(ocf::heartbeat:LVM):	Started host2.example.com
     my_fs	(ocf::heartbeat:Filesystem):	Started host2.example.com
     VirtualIP	(ocf::heartbeat:IPaddr2):	Started host2.example.com
     Website	(ocf::heartbeat:apache):	Started host2.example.com

/var/log/messages
...
Jan 25 02:25:58 host1 pengine[1458]:    info: Website has failed 1 times on host2.example.com
Jan 25 02:25:58 host1 pengine[1458]: warning: Forcing Website away from host2.example.com after 1 failures (max=1)
...
Jan 25 02:25:58 host1 pengine[1458]:  notice:  * Move       my_lvm         ( host2.example.com -> host1.example.com )
Jan 25 02:25:58 host1 pengine[1458]:  notice:  * Move       my_fs          ( host2.example.com -> host1.example.com )
Jan 25 02:25:58 host1 pengine[1458]:  notice:  * Move       VirtualIP      ( host2.example.com -> host1.example.com )
Jan 25 02:25:58 host1 pengine[1458]:  notice:  * Recover    Website        ( host2.example.com -> host1.example.com )
...
Jan 25 02:41:00 host1 pengine[1458]:  notice: Clearing failure of Website on host2.example.com because it expired
Jan 25 02:41:00 host1 pengine[1458]:    info: Website has failed 1 times on host2.example.com
Jan 25 02:41:00 host1 pengine[1458]:  notice: Clearing failure of Website on host2.example.com because it expired
Jan 25 02:41:00 host1 pengine[1458]:  notice: Re-initiated expired calculated failure Website_monitor_10000 (rc=7, magic=0:7;16:179:0:7a8ad70e-ad05-403a-93bc-b174050386e3) on host2.example.com
...
Jan 25 02:41:00 host1 pengine[1458]:  notice:  * Move       my_lvm         ( host1.example.com -> host2.example.com )
Jan 25 02:41:00 host1 pengine[1458]:  notice:  * Move       my_fs          ( host1.example.com -> host2.example.com )
Jan 25 02:41:00 host1 pengine[1458]:  notice:  * Move       VirtualIP      ( host1.example.com -> host2.example.com )
Jan 25 02:41:00 host1 pengine[1458]:  notice:  * Move       Website        ( host1.example.com -> host2.example.com )
~~~

Expected results:

The resources move back to the original node after failure-timeout.

Additional info:

Comment 2 Ken Gaillot 2021-01-25 15:29:23 UTC

Hi,

This is a known limitation in the RHEL 7 Pacemaker version, documented in the reference guide:

    https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/high_availability_add-on_reference/s1-resourceopts-haar

The limitation was removed in RHEL 8.2. Due to the life cycle phase of RHEL 7, it will not be backported.

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