Fix wrong backup check for SQL Always on High availability Groups #518
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CheckmkCI
force-pushed
the
master
branch
2 times, most recently
from
875a494 to
3419412
Compare
|
Dear Checkmk Contributor! Unfortunately, we had to re-write our git-repo history, rendering your PR auto-closed. We will therefore rebase your PR onto the current master and reopen it again. Sorry for the inconvenience. |
|
Dear Contributor. Unfortunately, we learned that re-opening a PR which was force-rebased, is not possible (see isaacs/github#361). Therefore we kindly ask you to create a new PR for your change. We apologize for the circumstances and will implement technical measures to prevent such incidents in the future. |
|
recreated at #727 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bug reports
operating system name and version
SQL Always on High availability Groups on SQL Server 2019
Windows Server 2019
Detailed steps to reproduce the bug
Proposed changes
What is the expected behavior?
The Agent should return the Backup status, even if it is not the primary Server
What is the observed behavior?
The Agent does not return the Backup if it is not the Primary Replica
If it's not obvious from the above: In what way does your patch change the current behavior?
The Primary Server check is removed
Is this a new problem? What made you submit this PR (new firmware, new device, changed device behavior)?
The move of the datbase.