FIX: Pacemaker can't manage cluster resources in an Always On Availability Group in SQL Server

Applies to: SQL Server 2017 DeveloperSQL Server 2017 EnterpriseSQL Server 2017 Enterprise Core


Assume that you use Always On availability groups (AG) in Microsoft SQL Server 2017 on a Pacemaker cluster. You stop the fencing function by disabling the STONITH device. When you then stop one of the nodes in the cluster, the Pacemaker doesn't detect the stop and can't manage the node resources in the cluster.


The fix for this issue is included in the following update for SQL Server:

Cumulative Update 13 for SQL Server 2017


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


Learn about the standard terminology Microsoft uses to describe software updates.