Also hit upgrading 26.04 to 26.10 with ubuntu-release-upgrader 26.10.11. "sudo pro disable esm-apps esm-infra" worked around it.
In case it helps the review of https://code.launchpad.net/~zgrigoryan/ubuntu-release- upgrader/+git/ubuntu-release-upgrader/+merge/512289: the upgrader's Release-file check did run on the ESM sources, but only on the -updates suites. After the rewrite, the -updates stanzas were set to "Enabled: no" ("was disabled (no Release file)"), while the stonking-apps-security and stonking-infra-security stanzas stayed enabled, because updateDeb822Sources() skips the check for entries whose suites all end in -security or -backports: valid_suites = [s for s in entry.suites \ if s.rsplit('-', 1)[-1] not in ["backports", "security"]] https://git.launchpad.net/ubuntu-release- upgrader/tree/DistUpgrade/DistUpgradeController.py?id=d09d661750e42d2cb6da3c9ada3d772f22e2bbb3#n1051 The merge proposal avoids that path for interim targets by not mapping the ESM pockets at all. _Drafted by Claude (Anthropic AI assistant)._ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2084208 Title: do-release-upgrade fails when esm is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2084208/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
