RHBA-2019:0196 - Bug Fix Advisory

Topic

Updated pacemaker packages that fix several bugs are now available for Red Hat Enterprise Linux 7.

Description

The Pacemaker cluster resource manager is a collection of technologies working together to maintain data integrity and application availability in the event of failures.

This update fixes the following bugs:

• Previously, the "pcs resource refresh" command or the "pcs resource cleanup" command with a failed resource sometimes failed to wait for results from all nodes. As a consequence, those resources were not cleaned on all nodes. With this update, the problem has been fixed, and Pacemaker now cleans resources on all nodes. (BZ#1664242)
• Previously, when a resource needed to be moved to a node whose Pacemaker Remote connection was starting, the resource stop and the connection start were scheduled in parallel. If the connection start failed, the resource stop still succeeded. As a consequence, the service experienced downtime. With this update, the resource stop is now scheduled after the connection start in such a situation. As a result, the resource remains running where it is if the connection start fails. (BZ#1664243)
• Previously, the originator of the operation was not informed of its completion when a resource was cleaned up, refreshed, or removed from the configuration while an operation was in progress on that resource. As a consequence, the cluster was blocked from responding to new events for a couple of minutes, and the operation was then considered timed out. This sometimes led to fencing: for example, if the operation was a stop. With this update, the originator is now directly notified of the result, and the cluster is able to respond to new events. (BZ#1665816)

Users of pacemaker 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.

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.6 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.6 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 Resilient Storage for Power, little endian 7 ppc64le
• Red Hat Enterprise Linux Resilient Storage for Power, little endian - Extended Update Support 7.6 ppc64le
• Red Hat Enterprise Linux High Availability for Power, little endian 7 ppc64le
• Red Hat Enterprise Linux High Availability for Power, little endian - Extended Update Support 7.6 ppc64le
• Red Hat Enterprise Linux High Availability for Power LE - Update Services for SAP Solutions 7.6 ppc64le
• 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 - Extended Life Cycle Support 7 x86_64
• Red Hat Enterprise Linux Resilient Storage for x86_64 - Extended Life Cycle Support 7 x86_64
• Red Hat Enterprise Linux High Availability for IBM Power, little endian - Extended Life Cycle Support 7 ppc64le
• Red Hat Enterprise Linux Resilient Storage for IBM Power, little endian - Extended Life Cycle Support 7 ppc64le

Fixes

• BZ - 1664242 - Refreshing an unmanaged resource does not clean up its state entirely [rhel-7.6.z]
• BZ - 1665816 - Regression: Cleanup when operation in progress delays cluster response [rhel-7.6.z]

CVEs

(none)

References

(none)