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

Dependency issues on debian based deployment #35

Closed
ebonharme opened this issue Nov 28, 2016 · 2 comments
Closed

Dependency issues on debian based deployment #35

ebonharme opened this issue Nov 28, 2016 · 2 comments

Comments

@ebonharme
Copy link

ebonharme commented Nov 28, 2016

I've noticed that my deployments were failing recently as what is presumably a release containing a security issue was removed from the Ubuntu repositories. #34 should fix.

@hush-hush
Copy link
Member

Hi @ebonharme, thanks for opening this issue !

Updating the apt cache every hour maybe a little aggressive, especially since network operation are prone to fail.
But the state=latest is actually not needed, a simple state=present would fix the problem you raised without forcing a cache update.

I will update that today, feel free to add a comment if you have anything to add. Thanks!

@ebonharme
Copy link
Author

Thanks for attending to this issue @hush-hush. In my specific use case, it's rare that I go and reconfigure agent but good thinking. state=present is good. Closing

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

2 participants