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
This happens on debian bookworm:
At the start of every agent run, the puppet agent seems to change the ownership of /var/cache/puppet to puppet:puppet
Deploying puppet::server::config causes the ownership to be changed to root:root
This change in ownership then causes a restart of puppetserver, which is kindof annoying to have happening on every puppet run.
I'm not sure why vardir is set to ownership root:root, is there any harm in having it owned by user puppet?
The text was updated successfully, but these errors were encountered:
stop forcing root ownership of vardir
041b85e
this should fix theforeman#922
Successfully merging a pull request may close this issue.
This happens on debian bookworm:
At the start of every agent run, the puppet agent seems to change the ownership of /var/cache/puppet to puppet:puppet
Deploying puppet::server::config causes the ownership to be changed to root:root
This change in ownership then causes a restart of puppetserver, which is kindof annoying to have happening on every puppet run.
I'm not sure why vardir is set to ownership root:root, is there any harm in having it owned by user puppet?
The text was updated successfully, but these errors were encountered: