You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 10, 2019. It is now read-only.
as it doesn't do anything? It just starts the service on every puppet run:
Notice: /Stage[main]/Unattended_upgrades/Service[unattended-upgrades]/ensure: ensure changed 'stopped' to 'running'
Debug: /Stage[main]/Unattended_upgrades/Service[unattended-upgrades]: The container Class[Unattended_upgrades] will propagate my refresh event
Info: /Stage[main]/Unattended_upgrades/Service[unattended-upgrades]: Unscheduling refresh on Service[unattended-upgrades]
OS: Debian Jessie
The text was updated successfully, but these errors were encountered:
It's a question. I suppose this behavior has some purpose, otherwise it wouldn't be there. If there is no reason to have the service "running", I will prepare a pull request.
At the time this module was written, the service was required to run unattended-upgrades. Please feel free to test if its still required and report your results.
I think @pschichtel is going to open a PR to address this issue. I don't think that there is a reason to have the service running any more, but I don't actively use Puppet any more, so I need a PR with the fix and tests.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Checking the unattended-upgrades init script I can see:
Is it then required to have:
as it doesn't do anything? It just starts the service on every puppet run:
OS: Debian Jessie
The text was updated successfully, but these errors were encountered: