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

Add possibility to define watchdog_device resource #454

Merged
merged 3 commits into from
Mar 2, 2021

Conversation

dlucredativ
Copy link
Contributor

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

@bastelfreak
Copy link
Member

We somehow need to fix #455 before we can merge this :(

@@ -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,
Copy link
Member

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:

Suggested change
Optional[String] $watchdog_device = undef,
Optional[Variant[Stdlib::Absolutepath, Enum['off']]] $watchdog_device = undef,

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can do.

@vox-pupuli-tasks
Copy link

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

@vox-pupuli-tasks
Copy link

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

@damluk
Copy link

damluk commented Apr 9, 2020

We somehow need to fix #455 before we can merge this :(

#455 is still open, nevertheless there have been other PRs merged, as I had to rebase. Is there a chance this one will be too, anytime soon?

Thanks.

@vox-pupuli-tasks
Copy link

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?
If you need any help, you can reach out to us on our IRC channel voxpupuli on Freenode or our Slack channel voxpupuli at slack.puppet.com.
You can find my sourcecode at voxpupuli/vox-pupuli-tasks

@ekohl
Copy link
Member

ekohl commented May 29, 2020

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.

@vox-pupuli-tasks
Copy link

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

@dlucredativ
Copy link
Contributor Author

@timdeluxe do you still have a use case for this MR? It has outlived its purpose on Debian stable.

@timdeluxe
Copy link
Contributor

@dlucredativ
I needed to search context first, i think you refer to this: corosync/corosync@b7b318b

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:
static char *watchdog_device = "/dev/watchdog";
We did not plan to Ubuntu 20 yet and there is no pressure yet - standard support of Ubuntu 18 goes until April 2023, so that is still a while and i think this corosync module should support 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.

@bastelfreak
Copy link
Member

looks good to me. @ekohl any objections against merging?

@timdeluxe
Copy link
Contributor

@dlucredativ Can you resolve the merge conflict please so this could get finally merged?

@timdeluxe
Copy link
Contributor

Thanks @dlucredativ, that was fast!

@ekohl Can this be merged and released now?

manifests/init.pp Outdated Show resolved Hide resolved
spec/classes/corosync_spec.rb Outdated Show resolved Hide resolved
templates/corosync.conf.erb Outdated Show resolved Hide resolved
Co-authored-by: Ewoud Kohl van Wijngaarden <ewoud@kohlvanwijngaarden.nl>
@dlucredativ
Copy link
Contributor Author

@ekohl do you prefer your suggestions to remain in a separate commit or should I fixup them into de92e05?

Copy link
Member

@ekohl ekohl left a 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.

@ekohl
Copy link
Member

ekohl commented Mar 2, 2021

Merging now that CI has completed. Thanks!

@ekohl ekohl merged commit 9bef543 into voxpupuli:master Mar 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants