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

Consider apt lock handling #446

Open
ripleymj opened this issue Feb 20, 2021 · 2 comments · May be fixed by #475
Open

Consider apt lock handling #446

ripleymj opened this issue Feb 20, 2021 · 2 comments · May be fixed by #475
Assignees
Milestone

Comments

@ripleymj
Copy link
Member

Ansible now has recommendations for handling an existing apt lock, which may be more elegant than our current methods: ansible/ansible#73079

@ripleymj ripleymj self-assigned this Feb 20, 2021
@ripleymj ripleymj added this to the Fall 2021 milestone Feb 20, 2021
@laurelmay
Copy link
Member

I am not sure if this will work for us. It seems like the only place we "handle" a conflict over the lock file is in ubuntu-build.json where we try to do it prior to the apt update there. I am not convinced I want to start adding this to every apt command throughout the repo either.

@laurelmay laurelmay linked a pull request Aug 29, 2021 that will close this issue
@ripleymj ripleymj modified the milestones: Fall 2021, Spring 2022 Sep 1, 2021
@laurelmay laurelmay modified the milestones: Spring 2022, Fall 2022 Jul 18, 2022
@laurelmay
Copy link
Member

It looks like the solution in that linked issue is no longer recommended and has been removed from the docs as of ansible/ansible#76243. As of 2.12, instead specifying lock_timeout is preferred, though that already has a default of 60. This is notably a bit different from outright stopping unattended-upgrades.service and infinitely waiting for apt to finish, but maybe it's enough for our use case?

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

Successfully merging a pull request may close this issue.

2 participants