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.

Description of problem:

[root@airfrance-2 ~]# pcs resource help cleanup

Usage: pcs resource cleanup...
    cleanup [<resource id>]


Should beL cleanup  [<resource id>]  [<node id>]

Version-Release number of selected component (if applicable):

Name        : pcs
Version     : 0.9.143

How reproducible:

100%

Steps to Reproduce:
1. pcs resource cleanup killer airfrance-2
2.
3.

Actual results:

[root@airfrance-2 ~]# pcs resource cleanup killer airfrance-2
Waiting for 2 replies from the CRMd.. OK
Cleaning up killer on airfrance-1, removing fail-count-killer
Cleaning up killer on airfrance-2, removing fail-count-killer
Cleaning up killer on airfrance-3, removing fail-count-killer

Expected results:

[root@airfrance-2 ~]# pcs resource cleanup killer airfrance-2
Waiting for 1 replies from the CRMd.. OK
Cleaning up killer on airfrance-2, removing fail-count-killer

Additional info:

Use the following option for crm_resource:

       -N, --node=value
              Host uname

--node parameter has been added to "pcs resource cleanup" command already due to bz1220512

This is current upstream pcs behavior:
[root@rh72-node1:~/devel/pcs/pcs]# ./pcs resource cleanup dummy --node rh72-node1 --debug
Running: /usr/sbin/crm_resource --cleanup --resource dummy --node rh72-node1
Finished running: /usr/sbin/crm_resource --cleanup --resource dummy --node rh72-node1
Return value: 0
--Debug Output Start--
Waiting for 1 replies from the CRMd. OK
Cleaning up dummy on rh72-node1, removing fail-count-dummy

--Debug Output End--
Waiting for 1 replies from the CRMd. OK
Cleaning up dummy on rh72-node1, removing fail-count-dummy


I am closing this as a duplicate. If I am missing something here, feel free to reopen. Thanks.

*** This bug has been marked as a duplicate of bug 1220512 ***