-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
github actions are broken for "ubuntu-18.04" bionic. "Mirror sync in progress?" error #323
Comments
As this is happening so often and it is not planned to be fixed any time soon (see dotnet/core#4167), probably the best thing for downstream GitHub Actions users that are not interested in It would be great if the use of these apt repos in GitHub Actions could opt-in, instead of opt-out, to reduce the amount of boilerplate GitHub Actions necessary in every repo. |
Microsoft apt repos break apt-get update for several days at every update, and there is no plan to fix these. As we are not using the repos, the best course of action is just to remove them. See: * actions/runner-images#323 * dotnet/core#4167
Example step to remove the apt repos, from https://github.community/t5/GitHub-Actions/ubuntu-latest-Apt-repository-list-issues/m-p/41138/highlight/true#M4501 : # Remove apt repos that are known to break from time to time
# See https://github.com/actions/virtual-environments/issues/323
- name: Remove broken apt repos [Ubuntu]
if: matrix.os == 'ubuntu-latest'
run: |
for apt_file in `grep -lr microsoft /etc/apt/sources.list.d/`; do sudo rm $apt_file; done |
Microsoft apt repos break apt-get update for several days once in a while. As there is currently no plan to fix these outages from Microsoft side (see dotnet/core#4167) and we are not using the repos, the best course of action is just to remove them. See: * actions/runner-images#323
@traversaro that works for me. Thank you for this tip. I'll leave this open for github to triage (or escalate/transfer to Microsoft teams) as they see fit. After all, the fix that works for you and for me is still unacceptable for anyone who does need |
Microsoft apt repos break apt-get update for several days at every update, and there is no plan to fix these. As we are not using the repos, the best course of action is just to remove them. See: * actions/runner-images#323 * dotnet/core#4167
Microsoft apt repos break apt-get update for several days at every update, and there is no plan to fix these. As we are not using the repos, the best course of action is just to remove them. See: * actions/runner-images#323 * dotnet/core#4167
Microsoft apt repos break apt-get update for several days at every update, and there is no plan to fix these. As we are not using the repos, the best course of action is just to remove them. See: * actions/runner-images#323 * dotnet/core#4167
Microsoft apt repos break apt-get update for several days at every update, and there is no plan to fix these. As we are not using the repos, the best course of action is just to remove them. See: * actions/runner-images#323 * dotnet/core#4167
Microsoft apt repos break apt-get update for several days at every update, and there is no plan to fix these. As we are not using the repos, the best course of action is just to remove them. See: * actions/runner-images#323 * dotnet/core#4167
Microsoft apt repos break apt-get update for several days at every update, and there is no plan to fix these. As we are not using the repos, the best course of action is just to remove them. See: * actions/runner-images#323 * dotnet/core#4167
Hello, @pestophagous |
Hey @al-cheb, thanks for taking an interest. Indeed dotnet/core#4179 is closed (though I would not say fixed), but it is worth copy-pasting the last thing noted on that ticket:
dotnet/core#4167 is still open. The flakiness is the bug. And in that sense, the bug still exists. The fact that However, the bug seems to belong to a non-github Microsoft team and not to github directly, so I agree with you that closing this github ticket for now is kind of our only option. Lastly, however, I will also echo what @traversaro said here earlier:
|
Describe the bug
A continuous integration action is failing at an early step when I call
sudo apt-get update
The error:
Area for Triage:
Containers + Packages + Ubuntu bionic + apt
Question, Bug, or Feature?:
Bug
Virtual environments affected
Expected behavior
This command should succeed:
sudo apt-get update
Actual behavior
A description with steps to reproduce the issue. If your have a public example or repo to share,
please provide the link.
.github/workflows/main.yml
that usesruns-on: ubuntu-18.04
sudo apt-get update
It seems this has happened in the recent past, then resolves in about a day:
dotnet/core#3221
dotnet/core#3988
Sorry to belabor the obvious, but this is disruptive to repositories that block merging of any PR until the actions succeed.
The text was updated successfully, but these errors were encountered: