Bug 1290830

I would like to piggy back on this bug to request a small number of additional PCS commands.  While working on the RHEL-OSP upgrade processes between 5->6 and 6->7, I often wanted a way to *programmatically* query the state of a Pacemaker managed service.  Specifically, I would like:

- To reliably test whether or not a resource exists.  This could be as simple as an appropriate return code from 'pcs resource status <resourcename>', so that I could do something like:

  if ! pcs resource status --quiet sshd; then
    pcs resource create sshd ...
  fi

  The above example suggests a '--quiet' flag to inhibit command output when one is only interested in existence.

- Test if a resource is started:

  pcs resource is-started sshd && echo "Resource is started"

- Test if a resource is stopped:

  pcs resource is-stopped sshd && echo "Resource is stopped"

- Test if a resource is failed:

  pcs resource is-failed sshd && echo "Resource is failed"

- Test if a resource is enabled:

  pcs resource is-enabled sshd && echo "Resource is enabled"

- Test if a resource is managed:

  pcs resource is-managed sshd && echo "Resource is managed"

For cloned resources or other multi-instance resources, maybe there should be --all and --any flags:

    pcs resource is-active --any sshd && echo "At least one sshd is active"
    pcs resource is-active --all sshd && echo "All sshd resources are active"

We also want to add the ability to wait for the resource to reach the desired state.  So something like this:

pcs resource is-active sshd --wait=30

Will not return until sshd is active or 30 seconds have passed.

Pacemaker feature which we depend on will not be ready in the 7.3 timeframe.

The pacemaker feature we depend on got postponed to 7.5.

Created attachment 1780673 [details]
proposed fix + tests

Updated commands:
pcs resource [status [<resource id | tag id>] [node=<node>] [--hide-inactive]]
pcs stonith [status [<resource id | tag id>] [node=<node>] [--hide-inactive]]
pcs status resources [<resource id | tag id>] [node=<node>] [--hide-inactive]

Test:
pcs resource status <resource id>

Test:

[root@r8-node-01 ~]# rpm -q pcs
pcs-0.10.8-2.el8.x86_64

[root@r8-node-01 ~]# pcs resource
  * d-01        (ocf::pacemaker:Dummy):  Stopped (disabled)
  * d-03        (ocf::pacemaker:Dummy):  Started r8-node-03
  * Clone Set: d-02-clone [d-02]:
    * Started: [ r8-node-01 r8-node-02 r8-node-03 ]
[root@r8-node-01 ~]# pcs tag
tagged
  d-01
  d-02
  d-03

[root@r8-node-01 ~]# pcs resource status d-01
  * d-01        (ocf::pacemaker:Dummy):  Stopped (disabled)
[root@r8-node-01 ~]# pcs status resources d-02
  * Clone Set: d-02-clone [d-02]:
    * Started: [ r8-node-01 r8-node-02 r8-node-03 ]
[root@r8-node-01 ~]# pcs resource status tagged
  * d-01        (ocf::pacemaker:Dummy):  Stopped (disabled)
  * d-03        (ocf::pacemaker:Dummy):  Started r8-node-03
  * Clone Set: d-02-clone [d-02]:
    * Started: [ r8-node-01 r8-node-02 r8-node-03 ]

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 (Low: pcs security, bug fix, and enhancement update), 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://access.redhat.com/errata/RHSA-2021:4142