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:
crm_simulate exits with "An invalid transition was produced" in the specific case described below.


Version-Release number of selected component (if applicable):
pacemaker-2.0.3-3.el8


How reproducible:
always


Steps to Reproduce:
1. Have two resources, d1 and d2.
2. Create an order constraint: start d1 then stop d2
3. Use crm_simulate to see what happens when d1 is disabled:
# pcs cluster cib > cib.xml
# pcs -f cib.xml resource disable d1
# crm_simulate --simulate --xml-file=cib.xml


Actual results:
crm_simulate returns 1 and exits with:
Executing cluster transition:
Transition failed: terminated
An invalid transition was produced

Created attachment 1644455 [details]
the original cib

this is the configuration of a cluster before disabling a resource

Created attachment 1644456 [details]
the updated cib

this cib contains the change to be simulated against the running cluster - d1 is disabled

Created attachment 1644457 [details]
crm_simulate output

This issue has been discovered when testing the safe-disable feature in pcs, see bz1631519#c17 and following comments there for more details.

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.

This is still a priority and will be reopened when developer time becomes available to address it