Assume that you use an AlwaysOn availability group (AG) in SQL Server 2017 on a Linux Pacemaker cluster. When you create the Pacemaker resource for the AG, Pacemaker demotes the current primary replica and does not promote any secondary replica to the primary. However, this issue happens only on some configurations of Pacemaker. 


This issue is fixed in the following cumulative update for SQL Server:

       Cumulative update 4 for SQL Server 2017

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:

Latest cumulative update 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 terminologythat Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!