- Issued:
- 2014-10-13
- Updated:
- 2014-10-13
RHBA-2014:1508 - corosync bug fix update
Synopsis
corosync bug fix update
Type/Severity
Bug Fix Advisory
Topic
Updated corosync packages that fix several bugs are now available for Red Hat Enterprise Linux 6.
Description
The corosync packages provide the Corosync Cluster Engine and C Application Programming Interfaces (APIs) for Red Hat Enterprise Linux cluster software.
The corosync packages have been upgraded to upstream version 1.4.7, which provides a number of bug fixes over the previous version. (BZ#1055584)
This update also fixes the following bugs:
-
If the cpg clients on active cluster nodes terminated while corosync on one of the nodes was paused, corosync did not update its internal information about cpg clients on other nodes properly after resuming. Consequently, that node considered the terminated cgp clients to be still up and running. This update modifies the cpg code to ensure that corosync properly updates information about the cpg membership in this situation. (BZ#1067043)
-
Previously, corosync terminated unexpectedly with a segmentation fault when started on a system with the /dev/shm device full. This happened because the corosync logging system, logsys, could not be properly initialized. This update improves handling of the logsys initialization, and corosync now displays an appropriate error message and exits gracefully if logsys cannot be initialized. (BZ#1011307)
-
Due to a list corruption bug in the Corosync Closed Process Group (CPG) API, corosync could terminate unexpectedly with a segmentation fault under some circumstances. To fix this problem, corosync has been modified to handle the CPG init and list removal functions in the same thread. (BZ#1025321)
-
Previously, corosync could abort without logging an error properly if it was unable to store a file to the user's file system. With this update, corosync now properly verifies whether a "blackbox" can be stored on the file system. A failure of a ring ID store operation is no longer handled by assert but corosync now tries to log an error and then exits gracefully. (BZ#1005179)
-
Previously, when using the InfiniBand Architecture (IBA) as a transport protocol for corosync, corosync could not properly handle the restart of the IBA subnet manager (SM). If the IBA SM was restarted, corosync was not able to start or became unresponsive if it was already running. A series of patches addressing this problem has been applied to corosync, and it now works properly as expected in this scenario. (BZ#1001210)
Users of corosync are advised to upgrade to these updated packages, which fix these bugs.
Solution
Before applying this update, make sure all previously released errata relevant to your system have been applied.
This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/articles/11258
Affected Products
| Product | Version | Arch |
|---|---|---|
| Red Hat Enterprise Linux Resilient Storage for x86_64 | 6 | x86_64 |
| Red Hat Enterprise Linux Resilient Storage for x86_64 | 6 | i386 |
| Red Hat Enterprise Linux Resilient Storage (for RHEL Server) from RHUI | 6 | x86_64 |
| Red Hat Enterprise Linux Resilient Storage (for RHEL Server) from RHUI | 6 | i386 |
| Red Hat Enterprise Linux High Availability for x86_64 | 6 | x86_64 |
| Red Hat Enterprise Linux High Availability for x86_64 | 6 | i386 |
| Red Hat Enterprise Linux High Availability (for RHEL Server) from RHUI | 6 | x86_64 |
| Red Hat Enterprise Linux High Availability (for RHEL Server) from RHUI | 6 | i386 |
Updated Packages
- corosync-debuginfo-1.4.7-1.el6.x86_64.rpm
- corosync-debuginfo-1.4.7-1.el6.i686.rpm
- corosync-1.4.7-1.el6.i686.rpm
- corosynclib-1.4.7-1.el6.x86_64.rpm
- corosynclib-devel-1.4.7-1.el6.i686.rpm
- corosynclib-devel-1.4.7-1.el6.x86_64.rpm
- corosync-1.4.7-1.el6.x86_64.rpm
- corosynclib-1.4.7-1.el6.i686.rpm
- corosync-1.4.7-1.el6.src.rpm
Fixes
- This content is not included.BZ - 1001210
- This content is not included.BZ - 1011307
- This content is not included.BZ - 1018232
- This content is not included.BZ - 1025321
- This content is not included.BZ - 1055584
- This content is not included.BZ - 1067043
CVEs
(none)
References
(none)
Additional information
- The Red Hat security contact is This content is not included.secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.
- Offline Security Data data is available for integration with other systems. See Offline Security Data API to get started.