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.

Fence-agents in RHEL6 are based on upstream version 3.1.x (same as in RHEL5). This helps us to be able to fix problems in both versions without a lot of additional work. Currently, fence-agents in RHEL7 (and upstream) are based on version 4.0.x - there were a lot of code cleanup so backporting patches is much more difficult than before. Problem with version 4.0.x is that it removes some non-standard (or deprecated) functions what can have impact on fence agents. This is the main reason why there is branch 3.9.x which incorporates all changes from 4.0.x versions but it does not apply patches (<10 small patches that removes code) that removes backward compatibility. It will be appreciated if we can use this version also in RHEL6.6+

@Steve:

There are 300+ patches in upstream as there was big refactoring and code is much more readable now. All changes that break backward compatibility were marked as 'COMPATIBILITY BREAK' in upstream (as we are upstream). With rebase we will have fixed all bugs found during 7.0/7.1 cycle (20+ bugs) and we will benefit with very similar codebase with RHEL7. Another improvement is fixing of CVE-2014-0104 
which was not addressed before in RHEL6, with this update only one fence agent is not fixed (fence_vmware_soap as it will require package that is not in RHEL6).

Backward compatibility is provided by set of 16 patches which are based on 'COMPATIBILITY BREAK' bugs.

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://rhn.redhat.com/errata/RHBA-2015-1350.html