-
Notifications
You must be signed in to change notification settings - Fork 15
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
sudo apt-get update
is flaky in Ubuntu 20.04
#34
Comments
Thanks for reporting this issue. We recently moved to a pull-through cache to improve some elements of performance and storage allocation. We configured a low Time-To-Live (TTL) for the metadata, but we see that is insufficient, as artifacts can fall out of sync (i.e. client gets a fresh InRelease file but a cached Packages file). We're expediting a fix to disable caching of these metadata files, to ensure requesters always get the latest metadata. |
We're still seeing this today with Ubuntu 22.04, e.g. https://github.com/nyaruka/mailroom/actions/runs/4147292294/jobs/7174029289 |
Thanks for reporting this, Rowan. We've developed the fix described above and are in the process of rolling it out to the mirrors. We must do this gradually (in accordance with Safe Deployment Procedures), but it is in progress. |
Still broken this morning.. hope the fix isn't too gradual...
|
We've actually rolled our delivery mechanism back due to a separate issue as of 1915UTC, so this should now be mitigated. Content should now be served via files on disk instead of pull-through cache. |
Thanks! |
Broken this afternoon..
|
Describe the issue
We're using
ubuntu-20.04-xl
in GitHub Actions. Runningsudo apt-get update
within the runner, it occasionally fails (i.e. flaky) although the probability is not high.When did the issue occur?
Not really sure, but we started encountering this issue ~5 days ago
Steps to Reproduce
Here's a GitHub Actions workflow file:
Actual Result
Running this gave us the error as follows, sometimes, saying
Hash Sum mismatch
on armhf packages:Expected Result
It always succeeds without any errors
Additional context
I reported this issue to actions/runner-images#7067, and was suggested opening an issue here.
The text was updated successfully, but these errors were encountered: