We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
After rebooting a client machine, I find in the first Puppet run:
Notice: /Stage[main]/Cvmfs::Fsck/Systemd::Unit_file[cvmfs-fsck.timer]/Service[cvmfs-fsck.timer]/ensure: ensure changed 'stopped' to 'running' (corrective) Info: /Stage[main]/Cvmfs::Fsck/Systemd::Unit_file[cvmfs-fsck.timer]/Service[cvmfs-fsck.timer]: Unscheduling refresh on Service[cvmfs-fsck.timer]
It seems the cvmfs-fsck.timer is deployed, but not enabled, so Puppet needs to re-activate it after each machine reboot.
cvmfs-fsck.timer
Should we also add enable => true here? https://github.com/cvmfs/puppet-cvmfs/blob/ca6eb1588ffd18c4fb01aad9866662cd4a19f5ab/manifests/fsck.pp#L19-L26
enable => true
The text was updated successfully, but these errors were encountered:
Yes it should be added.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
After rebooting a client machine, I find in the first Puppet run:
It seems the
cvmfs-fsck.timer
is deployed, but not enabled, so Puppet needs to re-activate it after each machine reboot.Should we also add
enable => true
here?https://github.com/cvmfs/puppet-cvmfs/blob/ca6eb1588ffd18c4fb01aad9866662cd4a19f5ab/manifests/fsck.pp#L19-L26
The text was updated successfully, but these errors were encountered: