RHBA-2014:1508 - 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

• 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 Resilient Storage for x86_64 6 x86_64
• Red Hat Enterprise Linux Resilient Storage 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
• 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

Fixes

• BZ - 1001210 - If rdma transport is used in cluster.conf, cman is unable to start after shutdown.
• BZ - 1011307 - corosync gives segmentation fault if /dev/shm is full
• BZ - 1018232 - gfs_controld[1438]: cpg_initialize error 100 after fenced node rejoins and mounts GFS2
• BZ - 1025321 - Corosync crash running cpg-init-load test
• BZ - 1055584 - Rebase corosync to newest upstream version from flatiron branch
• BZ - 1067043 - CPG membership may be inconsistent after node pause

CVEs

(none)

References

(none)