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 idea behind this request is to add a --simulate switch to
pcs that will print out the actions that the cluster will take
without actually doing it.  
                               
The background for this is that for an operator it is quite hard
to predict what the cluster will do after a "pcs ..." action.
Especially in complex clusters (think of the control plane in openstack)
with lots of constraints and resources this becomes an especially daunting 
task.                          
                               
An example output could be: 
$ pcs --simulate resource disable foo 
                               
The following actions will be undertaken:
1. resource A (depends on B) will stop on all nodes
2. resource B (depends on foo) will stop on all nodes
                               
                               
One of the side effects here would be to reuse crm_simulate and make
it completely user-friendly.

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 running crm_simulate to. These commands need to be overhauled to only push the CIB once at their end so pcs can ask pacemaker to simulate it. We can add a generic simulate mechanism to the new architecture and connect it to commands being moved to the 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.

FYI: crm_simulate in the Pacemaker upstream master branch (expected to land in upstream 2.1.0 and RHEL 8.5/9.0beta) now has an --output-as=xml option, to obtain reliably parseable output (the text output may change from release to release).