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.
The "pcs resource cleanup" command no longer generates unnecessary cluster load
The "pcs resource cleanup" command cleans the records of failed resource operations that have been resolved. Previously, the command probed all resources on all nodes, generating an unnecessary load on cluster operation. With this fix, the command probes only the resources for which a resource operation failed. The previous functionality of the "pcs resource cleanup" command has been replaced by the new "pcs resource refresh" command, which probes all resources on all nodes. For information on cluster resource cleanup, see https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html-single/high_availability_add-on_reference/#s1-resource_cleanup-HAAR.
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.
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