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:

A number of issues were encountered and patched while trying to scale pacemaker to hundreds of bundles (simulating a large number of OSP computes with IHA).

- [tools] Prevent disconnection during cleanups (by reading replies sooner)
- [tools] Don't cleanup on nodes not meeting the discovery conditions 
- [pacemaker] include remote nodes when scaling crmd's cib op timeouts
- [pacemaker] scale all cib operations with cluster size
- [pacemaker] provide override for cib op timeouts
- [pacemaker] Restore the ability to send the transition graph via the disk if it gets too big

Patches will be forthcoming

http://github.com/beekhof/pacemaker
 '~' represents a related but optional patch


+ e3b825a: Fix: crm_resource: Ensure we wait for all messages before exiting
+ 047a661: Fix: crm_resource: Have cleanup operate only on failures 
+ 9bc9f52: Fix: crm_resource: Don't cleanup on nodes not meeting the discovery conditions 
+ a79650a: Fix: crm_resource: Prevent disconnection from crmd during cleanup
+ b0ca9a1: Fix: Tools: Allow crm_resource to operate on anonymous clones in unknown states 
+ a646692: Fix: tools: Clean up everywhere if we don't know anything about the resource 
~ 870ebe5: Test: crm_resource: See what cleanup would have done for a saved configuration 
+ 88a2f64: Fix: crmd: Scale all cib operation timeouts 
+ 5bf05e5: Fix: crmd: Scale timeouts with the number of remotes too 
+ e77dfcb: Fix: PE: Restore the ability to send the transition graph via the disk if it gets too big

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/RHEA-2018:0860