fix: diagnose and fix the 26.09 maas smoke failure - #1386
Open
dholt wants to merge 1 commit into
Open
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
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.
Diagnose and fix the 26.09 MAAS smoke failure
What this is
MAAS controller role on Ubuntu 24.04 (Noble): the
add MAAS repositorytask applied the legacy defaultppa:maas/3.5, but MAAS 3.5 publishes no Noble packages, soapt_repositoryfailed on a missing Release file and the MAAS install never started. Normalize that legacy override toppa:maas/3.7when the host runs Ubuntu 24.04 or newer, while preserving any custommaas_repovalue. QA-fix scope only: touch only files needed for this failure.Verification
e98829e1eae8(different model vendors; strict verdict contract)