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
In the pre_tasks we do an apt update twice since for whatever reason this seemed to help avoid problems with these locks. This is something that isn't natively supported by the ansible package playbook. More information can be found here:
The best solution from that issue seemed to be the following:
- name: Wait for any possibly running unattended upgrade to finishraw: systemd-run --property="After=apt-daily.service apt-daily-upgrade.service" --wait /bin/true
So it would be worth seeing how that works.
The main benefit here is that we would save having to do an update twice in a row, although this doesn't take up much time relatively. It also just seems like a solution that makes sense since I'm not exactly sure why the double updated fixes things.
If the above code is implemented we should keep a close eye on future builds running into the problem again since the current solution has been working pretty reliably.
The text was updated successfully, but these errors were encountered:
In the
pre_tasks
we do anapt update
twice since for whatever reason this seemed to help avoid problems with these locks. This is something that isn't natively supported by the ansible package playbook. More information can be found here:ansible/ansible#25414
The best solution from that issue seemed to be the following:
So it would be worth seeing how that works.
The main benefit here is that we would save having to do an update twice in a row, although this doesn't take up much time relatively. It also just seems like a solution that makes sense since I'm not exactly sure why the double updated fixes things.
If the above code is implemented we should keep a close eye on future builds running into the problem again since the current solution has been working pretty reliably.
The text was updated successfully, but these errors were encountered: