-
Notifications
You must be signed in to change notification settings - Fork 94
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
service enable not set for varnish #140
Comments
Please do, I ran into the same problem just now. I'm just not sure why it suddenly appeared with an upgrade from puppet 3.7.2 to 3.8.7, but has not gone away with a downgrade… |
Nope, my problem doesn't seem to be related to this. I'll create a new ticket. |
@maxchk Close this, pls. Too many open issues let the module look bad. |
I still believe this is a real issue. The fix is very simple though. |
Let's fix it. Added PR 158. |
[Issue #140] Add "enable" parameter for varnish service
The current (master) manifests apparently sets this as default:
this will cause puppet to start up varnish if it's not already running - but it's not good enough, our new varnish VM did not pass the reboot test. Ref https://docs.puppet.com/puppet/4.9/types/service.html enable should also be set:
As for now I simply did a "systemctl enable varnish" on the server, it may be that I'll write up a pull request at a later stage if I get to it.
The text was updated successfully, but these errors were encountered: