Skip to content
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

Notice 'forcing apt update' on every run #161

Closed
sts opened this issue Sep 24, 2016 · 2 comments
Closed

Notice 'forcing apt update' on every run #161

sts opened this issue Sep 24, 2016 · 2 comments

Comments

@sts
Copy link

sts commented Sep 24, 2016

The module keeps notifying about a forced apt update runs on every run, although apt update is never executed.

Notice: forcing apt update for pc_repo PC1
Notice: /Stage[main]/Puppet_agent::Osfamily::Debian/Notify[pc_repo_force]/message: defined 'message' as 'forcing apt update for pc_repo PC1'
Debug: /Stage[main]/Puppet_agent::Osfamily::Debian/Notify[pc_repo_force]: The container Class[Puppet_agent::Osfamily::Debian] will propagate my refresh event
Debug: Class[Puppet_agent::Osfamily::Debian]: The container Stage[main] will propagate my refresh event
Debug: Class[Puppet_agent::Osfamily::Debian]: The container Class[Puppet_agent::Prepare] will propagate my refresh event
Debug: Class[Puppet_agent::Prepare]: The container Stage[main] will propagate my refresh event
Debug: Class[Puppet_agent::Prepare]: The container Class[Puppet_agent] will propagate my refresh event
Debug: Class[Puppet_agent]: The container Stage[main] will propagate my refresh event
Debug: Evicting cache entry for environment 'production'
# puppet --version
4.6.2
@jordigg
Copy link

jordigg commented Mar 9, 2017

Agree with this, this always flags machines are being on a "change" state.
I would avoid forcing apt updates. Providing a parameter to select if you want them or not would be beneficial. Otherwise leave it to the user's choice to run a system-wide apt-update when they need.

@MikaelSmith
Copy link
Contributor

This appears to be a duplicate of #132.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants