Implement option to disable watchdog device use of corosync #451
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
Updating fork
For background see ClusterLabs/crmsh#236
|
This probably depends on #450 |
|
@bastelfreak Sorry for being quite so long. I would suggest to close this PR unmerged in favor of PR #454 by @dlucredativ - i think his solution is better than mine. |
|
I thought that 450 wil fix the idempotency issues we have within docker, but that doesn't seem to be the case. I will close this PR. |
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.
Pull Request (PR) description
See ClusterLabs/crmsh#236:
On Ubuntu/Debian corosync is compiled with watchdog support. If a watchdog is loaded, corosync occupies it and you can not use sbd fencing device anymore, which also requires a watchdog device. This PR introduces an option to disable the use of watchdog by corosync.
This Pull Request (PR) fixes the following issues
n/a