RHBA-2015:0365 - Bug Fix Advisory

Topic

Updated corosync packages that fix several bugs and add two enhancements are now available for Red Hat Enterprise Linux 7.

Description

The corosync packages provide the Corosync Cluster Engine and C Application Programming Interfaces (APIs) for Red Hat Enterprise Linux cluster software.

This update fixes the following bugs:

• Previously, when the user set the consensus timeout value to a smaller value than the join timeout value, a suboptimal partition could occur. This update makes sure that the consensus timeout value is not smaller than the join timeout value, and in the described situation, corosync now shows an error message in configuration and refuses to start. (BZ#1074673)
• When the user dynamically added or removed nodes, the token timeout value could be too small. To fix this bug, dynamic token timeout has been implemented by adding the token_coefficient option. As a result, corosync now handles adding and removing of nodes correctly. (BZ#1078361)
• Previously, when the token timeout parameter was set to 10 or more seconds, corosync could need a longer time to create the initial membership. Nevertheless, the init script waited for initial membership for 10 seconds at maximum, which caused the init script to return an error message. This update enables the user to configure the time for initial membership manually, and increases the default value up to 60 seconds. (BZ#1078363)
• When the user reloaded the corosync configuration file with a different number of nodes and with the votequorum service enabled, the following error message was logged:

configuration error: nodelist or quorum.expected_votes must be configured!

With this update, the votequorum() reconfigure function is called after the whole reload is finished, and the error messages are thus no longer returned. (BZ#1085468)

• When the user file system became full and corosync was thus unable to store files, corosync could terminate unexpectedly. However, no proper error message was returned. A patch has been applied to fix this bug, and corosync now exits gracefully with an error message in the aforementioned situation. (BZ#1108525)
• When the user set an integer option in the corosync.conf file to a value out of the boundaries, the integer was parsed and overflew. However, corosync did not return an error message informing the user. With this update, integer boundaries are properly checked, and if the boundaries are exceeded, corosync now shows an error message during configuration file parsing. (BZ#1108708)
• When corosync received the SIGABRT or the SIGSEGV signals or when the user executed the "corosync -f" command, the files in the /dev/shm/ directory created by corosync were not deleted, resulting in loss of space in /dev/shm. With this update, signal handlers are properly registered, thus fixing this bug. (BZ#1117911)
• When the corosync utility was configured with the IPv6 network and packet fragmentation was disabled on the NIC switch, no packets were delivered. This update implements a correct calculation of data fragment size, and packets are delivered as intended. (BZ#1136429)
• When the user started the corosync systemd unit with an invalid or missing corosync.conf file, the time to fail the unit could be very long. To fix this bug, the unit file calls the init script which checks the return code of the execution of corosync, which reduces the time for the systemd unit to fail to a few seconds. (BZ#1149916)

In addition, this update adds the following enhancements:

• This update adds an extra option for the auto_tie_breaker quorum feature. This option allows more flexibility in setting tie breaker nodes and allows the user to number their nodes in a way that suits their configuration. (BZ#1059607)
• With this update, the corosync udpu transport automatically sends messages only to the appropriate members, and thus avoids sending messages to missing members when it is not required. (BZ#1069254)

Users of corosync are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Solution

Before applying this update, make sure all previously released errata
relevant to your system have been applied.

For details on how to apply this update, refer to:

https://access.redhat.com/articles/11258

Affected Products

• Red Hat Enterprise Linux High Availability for x86_64 7 x86_64
• Red Hat Enterprise Linux High Availability for x86_64 - Extended Update Support 7.7 x86_64
• Red Hat Enterprise Linux High Availability for x86_64 - Extended Update Support 7.6 x86_64
• Red Hat Enterprise Linux High Availability for x86_64 - Extended Update Support 7.5 x86_64
• Red Hat Enterprise Linux High Availability for x86_64 - Extended Update Support 7.4 x86_64
• Red Hat Enterprise Linux High Availability for x86_64 - Extended Update Support 7.3 x86_64
• Red Hat Enterprise Linux Resilient Storage for x86_64 7 x86_64
• Red Hat Enterprise Linux Resilient Storage for x86_64 - Extended Update Support 7.7 x86_64
• Red Hat Enterprise Linux Resilient Storage for x86_64 - Extended Update Support 7.6 x86_64
• Red Hat Enterprise Linux Resilient Storage for x86_64 - Extended Update Support 7.5 x86_64
• Red Hat Enterprise Linux Resilient Storage for x86_64 - Extended Update Support 7.4 x86_64
• Red Hat Enterprise Linux Resilient Storage for x86_64 - Extended Update Support 7.3 x86_64
• Red Hat Enterprise Linux High Availability (for RHEL Server) from RHUI 7 x86_64
• Red Hat Enterprise Linux Resilient Storage (for RHEL Server) from RHUI 7 x86_64
• Red Hat Enterprise Linux High Availability for x86_64 - Update Services for SAP Solutions 7.7 x86_64
• Red Hat Enterprise Linux High Availability for x86_64 - Update Services for SAP Solutions 7.6 x86_64
• Red Hat Enterprise Linux High Availability for x86_64 - Update Services for SAP Solutions 7.4 x86_64
• Red Hat Enterprise Linux High Availability for x86_64 - Update Services for SAP Solutions 7.3 x86_64
• Red Hat Enterprise Linux High Availability for x86_64 - Extended Life Cycle Support 7 x86_64
• Red Hat Enterprise Linux Resilient Storage for x86_64 - Extended Life Cycle Support 7 x86_64

Fixes

• BZ - 1059607 - [RFE] Make auto_tie_breaker node configurable
• BZ - 1078361 - Implement dynamic token timeout and make it default
• BZ - 1078363 - Handle corosync initialization timeout in init script
• BZ - 1085468 - scary messages on corosync config reload
• BZ - 1108508 - totemsrp: Fix typo with cont gather
• BZ - 1108511 - Corosync mon service contains various problems
• BZ - 1108522 - Various small fixes for RHEL 7.1 (corosync rebase)
• BZ - 1108525 - Fix corosync behavior when disk is full
• BZ - 1108708 - Config parser: Properly check integer values
• BZ - 1117911 - Logsys file leaks in /dev/shm after sigabrt, sigsegv and when running corosync -v
• BZ - 1149916 - 'systemctl start corosync.service' takes 60 second to time out when there is no corosync.conf file

CVEs

(none)

References

• http://www.redhat.com/security/updates/classification/#normal