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.

When translating a "live test" provided by booth upstream from using crm
commands to pcs equivalents, I've noticed that "pcs resource cleanup" is
missing "--wait" switch while it makes sense there.  This would likely
deserve close inspection so as to identify other commands not covered
with this synchronous handling enforcer (useful in 3rd party scripting).

+++ This bug was initially created as a clone of Bug #1188571 +++

I will piggyback this bugzilla with a need I have as well ;)

Namely in some OSP upgrade scripts I need pcs property set maintenance-mode=true and I need a guarantee in my scripts that it has been done and that the property is set on each cluster node. (Right now I work around it via crm_resource --wait) but it would be nice to have this --wait for all/most pcs commands.

This is not easy to do because many commands push the CIB several times and therefore there is not a single point at the end of the commands to put the waiting to. These commands need to be overhauled to only push the CIB once at their end so pcs can wait for pacemaker to process it. We are working on this continuously as we are moving commands to new architecture.

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.