Public bug reported: On Ubuntu 24.04 LTS (amd64), APT 2.8.3 intermittently fails to refresh package indexes from Ubuntu Snapshot Service. This blocks our pre- production patch validation because the upgrade simulation requires a successful index refresh.
**Steps to reproduce** Run `apt-get update --snapshot 20261029T020000Z`. We reproduced the failure directly on an affected Ubuntu host using normal DNS resolution and a fresh temporary APT lists directory. **Expected result** APT downloads and verifies all required indexes for the selected snapshot. **Actual result** On 5 November 2026, starting at **10:11:45 UTC**, we observed these responses from `185.125.189.37`: - HTTP 500 for `https://snapshot.ubuntu.com/ubuntu/20261029T020000Z/dists/noble-updates/InRelease` - HTTP 502 for `https://snapshot.ubuntu.com/ubuntu/20261029T020000Z/dists/noble-security/InRelease` - HTTP 502 for `https://snapshot.ubuntu.com/ubuntu/20261029T020000Z/dists/noble/main/binary-amd64/Packages` In a separate run, `185.125.189.69` served some indexes but returned HTTP 500 and 503 for others. The update reached the job's 600-second timeout. We also reproduced intermittent HTTP errors with direct `curl` requests from Ubuntu hosts outside CI. This report was filed under `apt` through Apport. Could you check the Ubuntu Snapshot Service logs for this time window and route the report to the team responsible for `snapshot.ubuntu.com` if appropriate? ** Affects: launchpad Importance: Undecided Status: New ** Tags: amd64 apport-bug noble ** Description changed: On Ubuntu 24.04 LTS (amd64), APT 2.8.3 intermittently fails to refresh package indexes from Ubuntu Snapshot Service. This blocks our pre- production patch validation because the upgrade simulation requires a successful index refresh. **Steps to reproduce** Run `apt-get update --snapshot 20261029T020000Z`. We reproduced the failure directly on an affected Ubuntu host using normal DNS resolution and a fresh temporary APT lists directory. **Expected result** APT downloads and verifies all required indexes for the selected snapshot. **Actual result** On 5 November 2026, starting at **10:11:45 UTC**, we observed these responses from `185.125.189.37`: - HTTP 500 for `https://snapshot.ubuntu.com/ubuntu/20261029T020000Z/dists/noble-updates/InRelease` - HTTP 502 for `https://snapshot.ubuntu.com/ubuntu/20261029T020000Z/dists/noble-security/InRelease` - HTTP 502 for `https://snapshot.ubuntu.com/ubuntu/20261029T020000Z/dists/noble/main/binary-amd64/Packages` - In a separate run, `185. + In a separate run, `185.125.189.69` served some indexes but returned + HTTP 500 and 503 for others. The update reached the job's 600-second + timeout. We also reproduced intermittent HTTP errors with direct `curl` + requests from Ubuntu hosts outside CI. - ProblemType: Bug - DistroRelease: Ubuntu 24.04 - Package: apt 2.8.3 - ProcVersionSignature: Ubuntu 6.8.0-138.138-generic 6.8.12 - Uname: Linux 6.8.0-138-generic x86_64 - ApportVersion: 2.28.3-0ubuntu0.1 - Architecture: amd64 - CasperMD5CheckResult: unknown - Date: Thu Nov 5 11:43:46 2026 - ProcEnviron: - LANG=es_ES.utf8 - PATH=(custom, user) - SHELL=/bin/bash - TERM=xterm-256color - XDG_RUNTIME_DIR=<set> - SourcePackage: apt - UpgradeStatus: No upgrade log present (probably fresh install) - modified.conffile..etc.logrotate.d.apt: [modified] - mtime.conffile..etc.logrotate.d.apt: 2026-05-28T08:57:08.728590 + This report was filed under `apt` through Apport. Could you check the + Ubuntu Snapshot Service logs for this time window and route the report + to the team responsible for `snapshot.ubuntu.com` if appropriate? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2173074 Title: Intermittent HTTP 500, 502 and 503 from snapshot.ubuntu.com on Ubuntu 24.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/2173074/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
