You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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?
Ansible now has recommendations for handling an existing apt lock, which may be more elegant than our current methods: ansible/ansible#73079
The text was updated successfully, but these errors were encountered: