[Ubuntu] put snapd auto refresh on hold #4768
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
/azp run Ubuntu1804, Ubuntu2004 |
|
Azure Pipelines successfully started running 2 pipeline(s). |
miketimofeev
approved these changes
Dec 19, 2021
7 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Canonical has informed us that GitHub actions generates too much traffic on their snapd servers, investigation has reveled that we inherit snap from the Azure Ubuntu images where snapd auto refresh is enabled (default settings) which causes lots of traffic on the reimage by automatically pulling all possible updates (if any). There is no way to disable auto refresh effectively but unregister snapd or mask the snapd systemd service. The most elegant solution is to put auto refresh on 60 days hold (maximum is 90 now) and calculate the deadline date as the date of an image generation + 60 days.
Related issue: https://github.com/actions/virtual-environments-internal/issues/3056
Check list