-
-
Notifications
You must be signed in to change notification settings - Fork 162
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
Add possibility to define watchdog_device resource #454
Conversation
We somehow need to fix #455 before we can merge this :( |
manifests/init.pp
Outdated
@@ -348,6 +353,7 @@ | |||
Optional[Enum['yes', 'no']] $clear_node_high_bit = undef, | |||
Optional[Integer] $max_messages = undef, | |||
Boolean $test_corosync_config = $corosync::params::test_corosync_config, | |||
Optional[String] $watchdog_device = undef, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you update this to something like:
Optional[String] $watchdog_device = undef, | |
Optional[Variant[Stdlib::Absolutepath, Enum['off']]] $watchdog_device = undef, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can do.
Dear @dlucredativ, thanks for the PR! This is pccibot, your friendly Vox Pupuli GitHub Bot. I noticed that your pull request contains merge conflict. Can you please rebase? You can find my sourcecode at voxpupuli/vox-pupuli-tasks |
Dear @dlucredativ, thanks for the PR! This is pccibot, your friendly Vox Pupuli GitHub Bot. I noticed that your pull request contains merge conflict. Can you please rebase? You can find my sourcecode at voxpupuli/vox-pupuli-tasks |
Dear @dlucredativ, thanks for the PR! This is Vox Pupuli Tasks, your friendly Vox Pupuli Github Bot. I noticed that your pull request has CI failures. Can you please have a look at the failing CI jobs? |
I've merged a major update to the tests. CentOS 7 still fails, but if you can rebase this and get everything else green this can be merged I think. |
Dear @dlucredativ, thanks for the PR! This is Vox Pupuli Tasks, your friendly Vox Pupuli GitHub Bot. I noticed that your pull request contains merge conflict. Can you please rebase? You can find my sourcecode at voxpupuli/vox-pupuli-tasks |
@timdeluxe do you still have a use case for this MR? It has outlived its purpose on Debian stable. |
@dlucredativ It is released with more up to date corosync releases (if i didn't get it wrong, since 2.99.0). Well, we still operate on Ubuntu 18, were i am pretty sure that it did not change there. To confirm it i gathered the sourcecode of the Ubuntu 18 package, and confirmed it: It would be nice to get a merge, because then i finally could switch back to the normal upstream release, instead of using a patched fork. |
looks good to me. @ekohl any objections against merging? |
@dlucredativ Can you resolve the merge conflict please so this could get finally merged? |
Thanks @dlucredativ, that was fast! @ekohl Can this be merged and released now? |
Co-authored-by: Ewoud Kohl van Wijngaarden <ewoud@kohlvanwijngaarden.nl>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm fine with a separate commit here.
Merging now that CI has completed. Thanks! |
This pull request allows to define a watchdog_device resource for corosync.
In early corosync versions, watchdog usage had to be explicitly turned off via the "off" keyword, while in recent versions its usage needs to be explicitly turned on via the device name e.g. "/dev/watchdog". Hence an Optional[String] seems a better choice than a Boolean.
Related to #451