-
Notifications
You must be signed in to change notification settings - Fork 224
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
SqlAGReplica: Tries to modify AG properties that were not specified #1244
Labels
bug
The issue is a bug.
Comments
Agree that is should be able to set these properties individually, labeling it as a bug. |
johlju
added
bug
The issue is a bug.
help wanted
The issue is up for grabs for anyone in the community.
labels
Oct 25, 2018
Hi, Any news on this ? |
I have a PR in to fix database ownership; after that's merged I will resubmit my PR for read-only routing which fixes (at least some of) this as part of it. So not long now. |
9 tasks
johlju
pushed a commit
that referenced
this issue
Mar 10, 2019
- Changes to SqlAG - Updated documentation on the behavior of defaults as they only apply when creating a group. - Changes to SqlAGReplica - AvailabilityMode, BackupPriority, and FailoverMode defaults only apply when creating a replica not when making changes to an existing replica. Explicit parameters will still change existing replicas (issue #1244). - ReadOnlyRoutingList now gets updated without throwing an error on the first run (issue #518).
johlju
removed
the
help wanted
The issue is up for grabs for anyone in the community.
label
Apr 25, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Details of the scenario you tried and the problem that is occurring
I'm trying to use SQLAGReplica to modify a property (ReadOnlyRoutingConnectionUrl) on an AG after it has been created.
This fails because the SQLAGReplica resource sets two default properties:
This means it tries to set them every time you access the AG even though you may only want to modify one property.
Verbose logs showing the problem
Suggested solution to the issue
The defaults on the parameters should be removed. If the resource detects it needs to add an AG Replica it can check for nulls in these properties and then set the same defaults. But if the replica is being modified, the existing settings won't be changed for these because there's no default set.
The DSC configuration that is used to reproduce the issue (as detailed as possible)
SQL Server edition and version the target node is running
2012
SQL Server PowerShell modules present on the target node
Current
The operating system the target node is running
2012
Version and build of PowerShell the target node is running
WMF 5.1
Version of the DSC module that was used ('dev' if using current dev branch)
dev
The text was updated successfully, but these errors were encountered: