Bionic ESM: +esm5 systemd packages return 404 from some esm.ubuntu.com
servers
The bionic fix for this bug, 237-3ubuntu10.57+esm5 in bionic-infra-security,
is listed in the current index. But some of the servers behind
esm.ubuntu.com return 404 for the package files, so whether apt upgrade works
depends on which address a machine reaches. On the machines that get a 404,
unattended-upgrades can't install esm5. Any machine that picked up +esm4 in
the roughly 14 hours it was current is then stuck on it, with the
dns_answer_new allocation bug that esm5 fixes.
The bionic-infra-security InRelease (Date: Thu, 15 Oct 2026 12:10:18 UTC)
lists 237-3ubuntu10.57+esm5 for systemd, libsystemd0, udev and the rest of
the systemd packages.
Below are HTTP status codes from a HEAD request to each IPv4 address that
esm.ubuntu.com resolves to, sent with valid Pro credentials and
curl --resolve, on 2026-10-15 at 15:11 UTC. All seven files were checked for
each version: systemd, systemd-sysv, libsystemd0, libnss-systemd,
libpam-systemd, udev and libudev1.
Address +esm2 (all 7) +esm5 (all 7)
185.125.190.23 200 404
185.125.190.24 200 404
185.125.190.75 200 200
91.189.91.46 200 200
91.189.91.47 200 200
Every file gave the same result on a given server. IPv6 addresses not
tested.
The path is:
https://esm.ubuntu.com/infra/ubuntu/pool/main/s/systemd/<pkg>_237-3ubuntu10.57+<ver>_amd64.deb
Timeline from the same client (via normal DNS round-robin):
- 01:26 UTC: esm5 downloaded fine; the Last-Modified on the cached .debs
is 2026-10-15 01:26:27-28 UTC.
- 14:07 UTC: systemd esm5 returned 404 while libsystemd0 esm5 still
downloaded.
- 15:01 UTC: systemd, libsystemd0 and udev esm5 all returned 404 from
185.125.190.24.
The files apt cached at 01:26 match the SHA256 hashes in the current
Packages index, so it doesn't look like esm5 was rebuilt. It looks like .23
and .24 are out of sync with the rest of the servers.
Repro (as root on an attached bionic machine):
apt-get update
apt-get download systemd=237-3ubuntu10.57+esm5
# -> 404 when esm.ubuntu.com resolves to 185.125.190.23/.24
Workaround until it's fixed: temporarily add "91.189.91.46 esm.ubuntu.com" to
/etc/hosts, run the upgrade, then remove the entry.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2170538
Title:
Ubuntu 24.04: systemd-resolved DNSSEC fails after root KSK rollover;
built-in trust anchor lacks key 38696
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2170538/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
