pacemaker (SL7)

Synopsis: Moderate: pacemaker security, bug fix, and enhancement update
Advisory ID: SLSA-2015:2383-1
Issue Date: 2015-11-19
CVE Numbers: CVE-2015-1867

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

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

With this update, the lrmd daemon now unsets the “NOTIFY_SOCKET” variable
in the described circumstances, and these error messages are no longer

* 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.

* 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.

* 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.

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.

* 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.

* 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.


– Scientific Linux Development Team