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:
When creating bundles (rabbit/galera/redis) with pcmk-1.1.19 code inside against a pcmk-1.1.18 cluster, we will experience crm_node -n hanging, because when pcs creates the bundle it will invoke the meta-data function. Doing so in this specific configuration will invoke crm_node -n which will hang.

By not invoking crm_node -n, everything is fine.

This is due to the newly introduced CRM_OP_NODE_INFO call and this very specific upgrade path.

Fix is here: https://github.com/ClusterLabs/resource-agents/pull/1173/

Verified, 

[root@controller-0 ~]# docker exec -it galera-bundle-docker-0 sh -c "rpm -q pacemaker resource-agents"
pacemaker-1.1.19-4.el7.x86_64
resource-agents-4.1.1-4.el7.x86_64
[root@controller-0 ~]# rpm -q pacemaker resource-agents
pacemaker-1.1.18-11.el7_5.3.x86_64
resource-agents-3.9.5-124.el7.x86_64

...
2018-08-01 08:22:38Z [overcloud]: CREATE_COMPLETE  Stack CREATE completed successfully

 Stack overcloud CREATE_COMPLETE 

Started Mistral Workflow tripleo.deployment.v1.get_horizon_url. Execution ID: 1d512b4e-a447-4d2b-9e13-0cdf0eb8bf4b
Overcloud Endpoint: http://10.0.0.106:5000/
Overcloud Horizon Dashboard URL: http://10.0.0.106:80/dashboard
Overcloud rc file: /home/stack/overcloudrc
Overcloud Deployed

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:3278