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.
* After the user displayed the list of STONITH devices or resources, their locations were not included. Now, the list also contains the locations of the devices and resources. (BZ#1174244)
Description of problem:
Currently "pcs stonith show" only shows if a stonith resource is started or stoppped, but not on which node it is running. since in most cases it is important that the stonith resource does not run on the node which it is supposed to fence it would be usefull if "pcs stonith show" would aslo show the node the stonith resource is currently running on.
Version-Release number of selected component (if applicable):
pcs-0.9.123-9.el6
How reproducible:
always
Steps to Reproduce:
1. configure some stonith resources
2. run "pcs stonith" or pcs stonith show"
3.
Actual results:
[root]# pcs stonith show
st-ipmi-node1 (stonith:fence_ipmilan): Started
st-ipmi-node2 (stonith:fence_ipmilan): Started
Expected results:
[root]# pcs stonith show
st-ipmi-node1 (stonith:fence_ipmilan): Started node2
st-ipmi-node2 (stonith:fence_ipmilan): Started node1
Additional info:
"pcs status already provides the information omn which nodes the stonith resources are running so it should be easy to integrate this info in the output of "pcs stonith":
[root@ls3244 ~]# pcs status
Cluster name: testcluster
Last updated: Mon Dec 15 14:37:28 2014
Last change: Mon Dec 15 14:36:32 2014
Stack: cman
Current DC: node1 - partition with quorum
Version: 1.1.11-97629de
2 Nodes configured
6 Resources configured
Online: [ node1 node2 ]
Full list of resources:
st-ipmi-node1 (stonith:fence_ipmilan): Started node2
st-ipmi-node2 (stonith:fence_ipmilan): Started node1
...
Created attachment 979670[details]
proposed fix
Test:
Before fix:
[root@rh66-node1:~]# pcs resource
dummy (ocf::heartbeat:Dummy): Started
delay (ocf::heartbeat:Delay): Started
After fix:
[root@rh66-node1:~]# pcs resource
dummy (ocf::heartbeat:Dummy): Started rh66-node1
delay (ocf::heartbeat:Delay): Started rh66-node2
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.
https://rhn.redhat.com/errata/RHBA-2015-1446.html