[build] Fix debian mirror snapshot timestamp not work issue. (#21758) #21767
Conversation
This file contains hidden or 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
…et#21758) Why I did it Recently microsoft owned debian mirror has an issue. It is using the latest timestamp '20250216'. And this snapshot is a bad snapshot. Bydesign we should use timestamp '20250130', which passed PR validation. Get:18 http://packages.trafficmanager.net/snapshot/debian-security/20250216T001420Z bullseye-security/non-free amd64 Packages [1164 B] Get:19 http://packages.trafficmanager.net/snapshot/debian-security/20250216T001420Z bullseye-security/main amd64 Packages [346 kB] Fetched 17.9 MB in 5s (3789 kB/s) Reading package lists... E: Failed to fetch http://packages.trafficmanager.net/snapshot/debian-security/20250216T001420Z/dists/bullseye-security/main/source/Sources.xz File has unexpected size (234932 != 234820). Mirror sync in progress? [IP: 13.107.246.71 80] Hashes of expected file: - Filesize:234820 [weak] - SHA256:99cbb6795504058c2b3b2355ad128d8ca7879c136ba8fc00f2813ea4d5e7d147 Release file created at: Sat, 15 Feb 2025 17:04:32 +0000 E: Some index files failed to download. They have been ignored, or old ones used instead. By design, we should use timestamp in https://github.com/sonic-net/sonic-buildimage/blob/master/files/build/versions/default/versions-mirror How I did it Fix debian mirror snapshot timestamp generate script.
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
liushilongbuaa
requested review from
qiluo-msft,
xumia and
lguohan
as code owners
liushilongbuaa
requested review from
wangxin
and removed request for
lguohan,
qiluo-msft and
xumia
wangxin
approved these changes
Feb 21, 2025
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.
Why I did it
PR21366 wants to use debian snapshot instead of version pinning to improve image quality. But it missed this change. Build is using latest debian snapshot instead of validated snapshot.
Now validated snapshot is '20250130'. details in this link. But we can find build is using '20250216', which is a bad snapshot. It breaks SONiC build since Feb 16.
Work item tracking
How I did it
Fix debian mirror snapshot timestamp generate script.
How to verify it
Which release branch to backport (provide reason below if selected)
Tested branch (Please provide the tested image version)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)