Unable to connect to azure.archive.ubuntu.com flaky failure on ubuntu-* strikes back #6894
Comments
|
We are also experiencing failed jobs such as this one: |
|
can confirm, these issues are happening very frequently in the last days |
|
You probably want |
|
Hello! There is nothing we can do about it from our side, these are the network issues on azure mirror out of our control. |
Workaround for mirror issues, see actions/runner-images#6894.
This is a workaround for a "503 Service Unavailable" error when executing the apt command. For #1480. See also: actions/runner-images#6894 Co-authored-by: Sutou Kouhei <[email protected]>
This could help with CI failures due to server connection problems. Suggested-by: actions/runner-images#6894 (comment) Signed-off-by: David Lechner <[email protected]>
Thanks for the reply @mikhailkoliada ! Back in 2020 (#675 (comment)) I think the GitHub Actions staff got in contact with Azure Apt mirrors teams to try to understand how to fix or at least mitigate this issue. Do you happen to know any contact/entry-point/issue tracker of the Azure Apt mirrors teams to report this problems? I definitely do not know enough about this and the possible implication at GitHub Actions scale, but if this problem is persisten could it make sense to switch to some other apt mirrors? |
|
Another idea I just had: as setting |
This seems to help with flaky azure mirror used in GitHub CI. See actions/runner-images#675 and actions/runner-images#6894
This seems to help with flaky azure mirror used in GitHub CI. See actions/runner-images#675 and actions/runner-images#6894
|
Setting retries seems to be working in most cases. As this issue re-appears, it might be reasonable to include it in the CI images to avoid everybody adding some workaround in the actions. Besides that, I assume there is a good reason for sticking with Azure mirror when it's so flaky. |
|
So I tried with https://github.com/ARM-software/lisa/actions/runs/3910931347/jobs/6683709991 At this point, I'm tempted to overwrite /etc/apt/sources.list with the official content, is there any reason I should not do that ? EDIT: this still fails with: EDIT2: Looks like the official mirrors get redirected by Github infra to their own azure mirrors. https://github.com/ARM-software/lisa/actions/runs/3911002422/jobs/6683867161 |
|
@mdrakiburrahman explains it best here - #675 (comment)
|
The CI is failing due to some flaky connection to the Ubuntu repository: > E: Failed to fetch <package> Connection failed [IP: <IP>] This has happened for other projects and the recommendation is to do retry those fetches: actions/runner-images#6894
Summary: The CI is failing due to some flaky connection to the Ubuntu repository: > E: Failed to fetch <package> Connection failed [IP: <IP>] This has happened for other projects and the recommendation is to do retry those fetches: actions/runner-images#6894 Pull Request resolved: #9366 Test Plan: The CI appears to be making it passed downloading with this change: https://github.com/facebook/hhvm/pull/9366/checks Reviewed By: Wilfred Differential Revision: D45871141 Pulled By: paulbiss fbshipit-source-id: 6b4aab816efb1b6f8a685f3ad8968ddee1fce525
Description
On some jobs (apparently in a non-deterministic way) commands such as
apt-get installorapt-get upgradefail with the following error:This is similar to the previous solved issue #675
Platforms affected
Runner images affected
Image version and build link
Examples:
Is it regression?
Yes. However, it is not easy to determine the latest sane version as it is a non-deterministic bug.
Expected behavior
apt-get installshould complete successfully.Actual behavior
apt-get installfails.Repro steps
Run any action that runs
sudo apt installseveral times.The text was updated successfully, but these errors were encountered: