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: | ||||
: | 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
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). [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 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 |