RHSA-2015:2383 - Security Advisory

Topic

Updated pacemaker packages that fix one security issue, several bugs, and
add two enhancements are now available for Red Hat Enterprise Linux 7.

Red Hat Product Security has rated this update as having Moderate security
impact. A Common Vulnerability Scoring System (CVSS) base score, which
gives a detailed severity rating, is available from the CVE link in the
References section.

Description

The Pacemaker Resource Manager is a collection of technologies working
together to provide data integrity and the ability to maintain
application availability in the event of a failure.

A flaw was found in the way pacemaker, a cluster resource manager,
evaluated added nodes in certain situations. A user with read-only access
could potentially assign any other existing roles to themselves and then
add privileges to other users as well. (CVE-2015-1867)

The pacemaker packages have been upgraded to upstream version 1.1.13, which
provides a number of bug fixes and enhancements over the previous version.
(BZ#1234680)

This update also fixes the following bugs:

• When a Pacemaker cluster included an Apache resource, and Apache's

mod_systemd module was enabled, systemd rejected notifications sent by
Apache. As a consequence, a large number of errors in the following format
appeared in the system log:

Got notification message from PID XXXX, but reception only permitted
for PID YYYY

With this update, the lrmd daemon now unsets the "NOTIFY_SOCKET" variable
in the described circumstances, and these error messages are no longer
logged. (BZ#1150184)

• Previously, specifying a remote guest node as a part of a group resource

in a Pacemaker cluster caused the node to stop working. This update adds
support for remote guests in Pacemaker group resources, and the described
problem no longer occurs. (BZ#1168637)

• When a resource in a Pacemaker cluster failed to start, Pacemaker updated

the resource's last failure time and incremented its fail count even if the
"on-fail=ignore" option was used. This in some cases caused unintended
resource migrations when a resource start failure occurred. Now, Pacemaker
does not update the fail count when "on-fail=ignore" is used. As a result,
the failure is displayed in the cluster status output, but is properly
ignored and thus does not cause resource migration. (BZ#1200849)

• Previously, Pacemaker supported semicolon characters (";") as delimiters

when parsing the pcmk_host_map string, but not when parsing the
pcmk_host_list string. To ensure consistent user experience, semicolons are
now supported as delimiters for parsing pcmk_host_list, as well.
(BZ#1206232)

In addition, this update adds the following enhancements:

• If a Pacemaker location constraint has the "resource-discovery=never"

option, Pacemaker now does not attempt to determine whether a specified
service is running on the specified node. In addition, if multiple location
constraints for a given resource specify "resource-discovery=exclusive",
then Pacemaker attempts resource discovery only on the nodes specified in
those constraints. This allows Pacemaker to skip resource discovery on
nodes where attempting the operation would lead to error or other
undesirable behavior. (BZ#1108853)

• The procedure of configuring fencing for redundant power supplies has

been simplified in order to prevent multiple nodes accessing cluster
resources at the same time and thus causing data corruption. For further
information, see the "Fencing: Configuring STONITH" chapter of the High
Availability Add-On Reference manual. (BZ#1206647)

• The output of the "crm_mon" and "pcs_status" commands has been modified

to be clearer and more concise, and thus easier to read when reporting
the status of a Pacemaker cluster with a large number of remote nodes and
cloned resources. (BZ#1115840)

All pacemaker users are advised to upgrade to these updated packages, which
correct these issues 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 Resilient Storage for IBM z Systems 7 s390x
• Red Hat Enterprise Linux High Availability for IBM z Systems 7 s390x
• 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

Fixes

• BZ - 1162727 - member weirdness when adding/removing nodes
• BZ - 1172539 - Node ends up in a reboot loop when a resource with the same name exists
• BZ - 1182244 - crm_resource --restart broken
• BZ - 1182614 - Logs full of: error: gio_poll_dispatch_update: Adaptor for descriptor 8 is not in-use
• BZ - 1187321 - pacemaker - libqb dependency needs update
• BZ - 1194475 - edge case causes colocation constraint not to be honored.
• BZ - 1200785 - pacemaker-cli requires pacemaker but does not depend on it
• BZ - 1200849 - crmd: Resource marked with failcount=INFINITY on start failure with on-fail=ignore
• BZ - 1203053 - Nagios metadata is missing
• BZ - 1205188 - debug-promote implementation
• BZ - 1206232 - fencing: Allow semi-colon delimiter for pcmk_host_list
• BZ - 1211370 - CVE-2015-1867 pacemaker: acl read-only access allow role assignment
• BZ - 1211833 - systemd resources are shut down before the cluster at reboot
• BZ - 1212647 - crm_resource -C works inconsistently with clearing resources on baremetal remote nodes
• BZ - 1225854 - Error in `/usr/sbin/crm_resource': free(): invalid pointer: 0x00007f7199482848
• BZ - 1234680 - Rebase Pacemaker to obtain pacemaker-remote fixes for OSP
• BZ - 1246291 - lrmd killed by SIGSEGV
• BZ - 1267265 - A change in "crm_resource --set-parameter is-managed" introduces regression for Clone and M/S resources

CVEs

• CVE-2015-1867

References

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