-
-
Notifications
You must be signed in to change notification settings - Fork 244
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
Restart system.d service during consul version update #489
Comments
Hi @123BLiN . Yes, you got it right: #381 (comment) |
Oh, thank you! The problem as I see it, is that we are not able to override this default behaviour for consul client nodes (not server nodes) So have this setting as an attirbute may be much appreciated, so I will try to leave this ticket open. |
This is likely something we could easily make configurable using the poise_service_options resource. It looks like this is overridable using node attributes as well. |
Hi there! Thanks for taking the time to submit an issue. We would happily accept a pull request to resolve this issue. If you need help or guidance on submitting, please don't hesitate to ask! If you need help, or just wish to talk through issue please join the Chef Community Slack and look for the #sous-chefs channel. Thanks, |
Marking stale due to inactivity. Remove stale label or comment or this will be closed in 7 days. Alternatively drop by the #sous-chefs channel on the Chef Community Slack and we'll be happy to help! Thanks, Sous-Chefs. |
Maybe I'm missing something, but I can not find this in the cookbook.
Is it expected that I need to manually restart service on linux on every node (centos 7) during version upgrade?
75f76d6
Is it possible to make this as an attribute to be able to override it in the wrapper?
What were the reasons for such decision?
Btw on windows upgrade works with restart.
The text was updated successfully, but these errors were encountered: