Created attachment 1352004 [details]
proposed fix

Test CLI:
* 'pcs resource cleanup' runs 'crm_resource --cleanup'
* 'pcs resource refresh' runs 'crm_resource --refresh'
* the same applies to 'pcs stonith cleanup | refresh'
* see bz1508350 comment 3 for details how to test these
* corresponding capabilities:
  pcs --version --full | tr ' ' "\n" | grep '^pcmk.resource.refresh$'
  pcs --version --full | tr ' ' "\n" | grep '^pcmk.stonith.refresh$'
* corresponding manpage / usage update


Test webUI - a resource detail page:
* for new pcsd: the old "cleanup" button has been replaced by "refresh" and "cleanup" which call corresponding crm_resource functionality
* for old pcsd (not supporting the pcmk.resource.refresh.one-resource capability): the old "cleanup" button has been renamed to "refresh". The point is an old pcsd can only run 'crm_resource --cleanup', which with pacemaker packages from the same release does the same as 'crm_resource --refresh' does now.

After fix:
[root@rhel75-node1 ~]# rpm -q pcs
pcs-0.9.162-1.el7.x86_64

> cli
[root@rhel75-node1 ~]# pcs resource cleanup --debug | grep crm_resource
Running: /usr/sbin/crm_resource --cleanup
Finished running: /usr/sbin/crm_resource --cleanup
[root@rhel75-node1 ~]# pcs resource refresh --debug | grep crm_resource
Running: /usr/sbin/crm_resource --refresh
Finished running: /usr/sbin/crm_resource --refresh
[root@rhel75-node1 ~]# pcs stonith cleanup --debug | grep crm_resource
Running: /usr/sbin/crm_resource --cleanup
Finished running: /usr/sbin/crm_resource --cleanup
[root@rhel75-node1 ~]# pcs stonith refresh --debug | grep crm_resource
Running: /usr/sbin/crm_resource --refresh
Finished running: /usr/sbin/crm_resource --refresh
[root@rhel75-node1 ~]# pcs --version --full | tr ' ' "\n" | grep '^pcmk.resource.refresh$'
pcmk.resource.refresh
[root@rhel75-node1 ~]# pcs --version --full | tr ' ' "\n" | grep '^pcmk.stonith.refresh$'
pcmk.stonith.refresh

> web UI
In resource detailed view there are buttons for “Reload” and “Refresh”

Tomas:

I did a reworking of the release note writeup -- based in part on the updates to the documentation.  Could you review the release note text?

Steven:

It looks perfect to me.

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://access.redhat.com/errata/RHBA-2018:0866