Unable to contact snap store on Xubuntu from Jammy to Noble
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
firefox (Ubuntu) |
Confirmed
|
High
|
Unassigned | ||
Noble |
Confirmed
|
High
|
Unassigned | ||
snapd (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Noble |
Confirmed
|
Undecided
|
Unassigned | ||
ubuntu-release-upgrader (Ubuntu) |
Invalid
|
High
|
Nick Rosbrook | ||
Noble |
Fix Released
|
High
|
Nick Rosbrook |
Bug Description
[Impact]
Upgrades from Jammy to Noble can fail if snap transition packages are installed after the new systemd has been unpacked, but before systemd-resolved has been unpacked.
In practice, this manifests on at least Xubuntu upgrades during the chromium-browser snap transition.
[Test Plan]
Without this fix, the snap store connectivity check will fail when installing the chromium-browser snap because systemd-resolved is not present, so DNS lookups fail during the connectivity check.
With the fix in place, the systemd-resolved stub resolver should be disabled during the upgrade so that DNS lookups succeed even when systemd-resolved is not yet unpacked on the system again.
So, to test this fix, we should run an upgrade on a Xubuntu 22.04 system:
$ do-release-upgrade -d
And verify that (a) the chromium-browser installation (and snap store connectivity check) succeeds, and (b) that the stub resolver is not in use during the upgrade.
$ cat /etc/resolv.conf
$ cat /run/systemd/
[Where problems could occur]
This patch disables the systemd-resolved stub resolver by writing a drop-in to
/run/systemd/
[Original Description]
When running `do-release-upgrade -d` on Jammy Xubuntu, the upgrade fails consistently at the `Installing the firefox snap` step.
This was first detected on Jenkins [1], then reproduced locally with `auto-upgrade-
[1]: https:/
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-
ProcVersionSign
Uname: Linux 5.15.0-88-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckR
CrashDB: ubuntu
CurrentDesktop: XFCE
Date: Fri Nov 17 18:24:22 2023
PackageArchitec
SourcePackage: ubuntu-
Symptom: ubuntu-
UpgradeStatus: No upgrade log present (probably fresh install)
tags: | added: rls-nn-incoming |
Changed in firefox (Ubuntu Noble): | |
milestone: | none → ubuntu-24.04-feature-freeze |
Changed in firefox (Ubuntu Noble): | |
milestone: | ubuntu-24.04-feature-freeze → ubuntu-24.04-beta |
Changed in firefox (Ubuntu Noble): | |
milestone: | ubuntu-24.04-beta → ubuntu-24.04 |
milestone: | ubuntu-24.04 → noble-updates |
Changed in snapd (Ubuntu Noble): | |
milestone: | none → noble-updates |
Changed in snapd (Ubuntu): | |
milestone: | none → noble-updates |
Changed in ubuntu-release-upgrader (Ubuntu Noble): | |
milestone: | none → ubuntu-24.04.1 |
tags: |
added: foundations-todo removed: rls-nn-incoming |
Changed in ubuntu-release-upgrader (Ubuntu): | |
importance: | Undecided → High |
assignee: | nobody → Nick Rosbrook (enr0n) |
description: | updated |
Changed in ubuntu-release-upgrader (Ubuntu Noble): | |
status: | Triaged → In Progress |
Looking at the log files this is happening when installing the firefox deb so the problem is likely there.
06:31:33 Selecting previously unselected package firefox. firefox_ 1%3a1snap1- 0ubuntu5_ amd64.deb ...
06:31:33 Preparing to unpack .../26-
06:31:33 => Installing the firefox snap
06:31:33 ==> Checking connectivity with the snap store
06:32:06 ===> Unable to contact the store, trying every minute for the next 30 minutes
06:47:28 ===> Still unable to contact the store, trying for another 20 minutes
07:02:51 ===> Still unable to contact the store, trying for another 10 minutes
07:16:00 Build timed out (after 60 minutes). Marking the build as failed.