Bug 1723778 - RFE: debug-monitor for stonith resources
Summary: RFE: debug-monitor for stonith resources
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pcs
Version: 8.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Tomas Jelinek
QA Contact: cluster-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-25 11:38 UTC by Josef Zimek
Modified: 2023-08-10 15:40 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 18803 0 None None None 2019-09-26 14:05:30 UTC

Description Josef Zimek 2019-06-25 11:38:23 UTC
Description of problem:

In rhel6 cluster we could use "fence_node -S <nodename>" to get status from fence device used by a cluster node. This help to determine if the configuration options used for fence device was correct. I do not believe a similar behavior exists in RHEL 7 or RHEL 8. 


  - How to test fence devices and fencing configuration in a Red Hat High Availability cluster? 
    https://access.redhat.com/solutions/18803

I believe we should open an RFE to request a similar option in RHEL 8. For example:

  # stonith_admin -S <nodename>
  or
  # pcs stonith debug-monitor <stonith id>

The command returns status output and if debug enabled, then print debug information to see why failed.

Comment 1 Ken Gaillot 2019-06-25 17:12:17 UTC
FYI pacemaker already has this capability with "stonith_admin --query <device-id>". It will run the device's "monitor" action, and if that fails, it will also run the device's "list" action (not sure why).

I'm assuming, based on the description, that the goal is more for the status of a particular fence device, without regard to any node name. The distinction is that in pacemaker, a node might be fenced by multiple fence devices -- which may be an "and" or "or" type of situation. So going by node name would be more complicated and require a new stonith_admin option. If we're just interested in a device, a pcs wrapper is all we need.

Comment 2 Ken Gaillot 2019-06-27 19:18:12 UTC
(In reply to Ken Gaillot from comment #1)
> FYI pacemaker already has this capability with "stonith_admin --query
> <device-id>". It will run the device's "monitor" action, and if that fails,
> it will also run the device's "list" action (not sure why).

I should point out the current limitations: it will only work when run on a node that is "running" the fence device; and it does not output anything, it just returns a status code.


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