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:

Pacemaker offers superior resource management and dependency tracking to rgmanager in clustered environments.  Effectively, it supersedes rgmanager's functionality in many ways while simultaneously providing users a staged upgrade path.

Resource agents written for rgmanager will work with pacemaker with minimal changes.

Unfortunately, pacemaker and rgmanager are not wire-compatible with one another, so there is no rolling upgrade path for rgmanager users for the rgmanager/pacemaker applications.

That said, with a conversion utility (#456897), it should be possible for pacemaker to provide the same services as rgmanager.

Additionally, because rgmanager now supports 'frozen' services, it should be possible to do a staged transition from rgmanager to pacemaker without affecting service availability:

 * Freeze all services
 * Kill rgmanager on all nodes
 * Convert cluster configuration, but leave all resources as 'unmanaged' in the pacemaker CIB (= config file)
 * Start pacemaker
 * Flip each resource to 'managed'

Version-Release number of selected component (if applicable): 6.0.0

Because a staged upgrade would be required, it may not be prudent to remove rgmanager from the distribution in RHEL6.

Pacemaker has not been included in Fedora yet, however, I expected it to go in to Fedora early after F11's release date.

*** This bug has been marked as a duplicate of bug 456895 ***