fix: fallbacks on current archive if old release not moved yet#313
Open
upils wants to merge 1 commit into
Open
fix: fallbacks on current archive if old release not moved yet#313upils wants to merge 1 commit into
upils wants to merge 1 commit into
Conversation
Signed-off-by: Paul Mars <paul.mars@canonical.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
When an Ubuntu release passes its end-of-life date, Chisel routes to
old-releases.ubuntu.com. However, the physical migration of the suite to that mirror is a manual admin operation that can lag the scheduled EOL — so for recently-EOL releases (e.g. 25.04, 25.10),old-releasesreturns 404 andarchive.Openfails, blocking rootfs cuts.This change makes
archiveURLreturn a fallback URL (the current archive) alongside the primary, andopenUbuntuprobesold-releasesonce up front: if it 404s, the current archive is pinned for the whole run.A new test (
TestOpenOldReleaseFallback) verifies that exactly one 404 occurs (the probe) and that subsequent fetches succeed against the current archive.Fix #312