Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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 915248

Summary:	Allow users to check or reset fail-count of a resource on a specific node
Product:	Red Hat Enterprise Linux 6	Reporter:	Frank Danapfel <fdanapfe>
Component:	pcs	Assignee:	Chris Feist <cfeist>
Status:	CLOSED ERRATA	QA Contact:	Cluster QE <mspqa-list>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.5	CC:	cluster-maint, fdinitto, rsteiger, slevine
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	pcs-0.9.64-1.el6	Doc Type:	Bug Fix
Doc Text:	Cause: There was no way to check (or reset) the failcount of a resource using pcs Consequence: Resource failcounts could not be viewed or reset using pcs and users would have to use other unsupported tools. Fix: Add 'pcs resource failcount show' & 'pcs resource failcount reset' Result: Users can now reset and view failcounts for specific resources	Story Points:	---
Clone Of:
Clones:	969568 (view as bug list)		Environment:
Last Closed:	2013-11-21 11:51:49 UTC	Type:	Bug
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:
Bug Blocks:	960054, 969568

Description Frank Danapfel 2013-02-25 09:49:34 UTC

Description of problem:
There is no way check or reset the fail-count of a resource on a specific node  with pcs.

Version-Release number of selected component (if applicable):
pcs-0.9.26-11.el6.noarch

A 'pcs resource failcount show <resource> <clusternode>' command should be added which does the equivalend of 'crm_failcount -N <clusternode> -r <resource> -G'

A 'pcs resource failcount reset <resource> <clusternode>' command should be added which does the equivalend of 'crm_failcount -N <clusternode> -r <resource> -D'

Comment 2 Chris Feist 2013-02-25 22:54:26 UTC

Added upstream

https://github.com/feist/pcs/commit/89ae2f0275c641d699e6b79f576cfc96bb3c0e70

Comment 3 Chris Feist 2013-02-25 22:55:03 UTC

One benefit in the upstream code is that you are not required to specify a node (if a node isn't specified it resets/shows the failcounts on all nodes in the cluster).

Comment 7 Chris Feist 2013-08-13 21:21:29 UTC

[root@ask-02 ~]# pcs resource fail -h

Usage: pcs resource fail...
    failcount show <resource id> [node]
        Show current failcount for specified resource from all nodes or
        only on specified node

    failcount reset <resource id> [node]
        Reset failcount for specified resource on all nodes or only on
        specified node

[root@ask-02 ~]# rpm -q pcs
pcs-0.9.64-1.el6.noarch

Comment 10 errata-xmlrpc 2013-11-21 11:51:49 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1633.html