Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

xSQLServerAlwaysOnAvailabilityGroup: Should Be Cluster Aware #868

Closed
randomnote1 opened this issue Oct 13, 2017 · 2 comments · Fixed by #890
Closed

xSQLServerAlwaysOnAvailabilityGroup: Should Be Cluster Aware #868

randomnote1 opened this issue Oct 13, 2017 · 2 comments · Fixed by #890
Labels
enhancement The issue is an enhancement request.

Comments

@randomnote1
Copy link
Contributor

Details of the scenario you tried and the problem that is occurring:
When the xSQLServerAlwaysOnAvailabilityGroup resource is applied to all of the nodes in a Failover Cluster Instance (FCI), the nodes will "fight" with each other while trying to create and configure the availability group.

The DSC configuration that is using the resource (as detailed as possible):
The following configuration applied to two or more nodes that host the FCI:

xSQLServerAlwaysOnAvailabilityGroup AddTestAG
{
    Ensure               = 'Present'
    Name                 = 'TestAG'
    SQLInstanceName      = $Node.SQLInstanceName
    SQLServer            = $Node.NodeName
    DependsOn            = '[xSQLServerEndpoint]HADREndpoint', '[xSQLServerPermission]AddNTServiceClusSvcPermissions'
    PsDscRunAsCredential = $SysAdminAccount
}

Version of the Operating System, SQL Server and PowerShell the DSC Target Node is running:
Any

What module (SqlServer or SQLPS) and which version of the module the DSC Target Node is running:
Any

Version of the DSC module you're using, or 'dev' if you're using current dev branch:
Any

@randomnote1
Copy link
Contributor Author

The resource should evaluate if the current node is actively hosting the SQL instance. If it is not hosting the instance, it should write a verbose message stating that it does not own the instance, and then silently exit.

@johlju johlju added enhancement The issue is an enhancement request. help wanted The issue is up for grabs for anyone in the community. labels Oct 13, 2017
@randomnote1
Copy link
Contributor Author

Starting this one

@johlju johlju added in progress The issue is being actively worked on by someone. and removed help wanted The issue is up for grabs for anyone in the community. labels Oct 16, 2017
johlju pushed a commit that referenced this issue Oct 20, 2017
- Changes to xSQLServerAlwaysOnAvailabilityGroup
  - Made the resource cluster aware. When ProcessOnlyOnActiveNode is specified,
    the resource will only determine if a change is needed if the target node
    is the active host of the SQL Server instance (issue #868).
@johlju johlju removed the in progress The issue is being actively worked on by someone. label Oct 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement The issue is an enhancement request.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants