Hello, Tracker: https://tracker.ceph.com/issues/79633 Ubuntu 24.04 LTS (noble) Debian packages were published for Tentacle 20.2.1 and 20.2.2, but are absent from 20.2.3 and 20.2.4. The rolling debian-tentacle repository has also lost its noble suite. Because 20.2.4 is the hotfix for CVE-2025-30156, CVE-2026-39944, CVE-2026-50152 and CVE-2026-54330, operators running cephadm on Ubuntu 24.04 currently have no upstream path to install patched host tooling (cephadm, ceph-common, ceph-volume) at a version matching the 20.2.4 container image. download.ceph.com coverage: Release jammy noble bookworm 20.2.0 present missing (pulled) present 20.2.1 present present present 20.2.2 present present present 20.2.3 present missing present 20.2.4 present missing present debian-tentacle (rolling) present missing present Squid (19.2.2–19.2.6) never published a noble suite. Noble in Tentacle therefore only exists for 20.2.1–20.2.2. 20.2.0 noble was published and then removed on 20 Nov 2025 because ceph-mgr crashed on Python 3.12 (tracker #73930). The announcement said Ubuntu 24.04 would return in a later point release. 20.2.1 and 20.2.2 did; 20.2.3 and 20.2.4 did not. Reproduce: curl -sI https://download.ceph.com/debian-20.2.2/dists/noble/Release # HTTP/1.1 200 OK curl -sI https://download.ceph.com/debian-20.2.3/dists/noble/Release curl -sI https://download.ceph.com/debian-20.2.4/dists/noble/Release # HTTP/1.1 404 Not Found curl -s https://download.ceph.com/debian-20.2.4/dists/ curl -s https://download.ceph.com/debian-tentacle/dists/ # bookworm/ jammy/ curl -s https://download.ceph.com/debian-20.2.2/dists/noble/main/binary-amd64/Packag... \ | grep -A3 -E '^Package: (cephadm|ceph-common|ceph-volume)$' # Version: 20.2.2-1noble The Ubuntu archive only has Squid 19.2.3-0ubuntu0.24.04.3 for noble, so download.ceph.com is the only upstream Tentacle source for this distro. Jammy 20.2.4-1jammy debs are not usable on noble (ABI). This looks like a release-matrix / publish gap, not "noble cannot build": v20.2.4 commit 7f793731f1b39eb4f465e960113d2363c311b964 Jenkins ceph-dev-pipeline/8318 https://shaman.ceph.com/builds/ceph/tentacle/7f793731f1b39eb4f465e960113d236... That job built jammy (20.2.4-1jammy), bookworm, Rocky 10, CentOS 9. It did not build noble. Those other distros were copied to download.ceph.com; noble was not. v20.2.3 commit 06c2f9c35b67055a8a6fb99d1be236b3c4832ace got a late noble CI rebuild on 27 Aug (20.2.3-1noble) that was never copied to debian-20.2.3/dists/noble/. tentacle/latest/ubuntu/noble currently points at that unpublished 20.2.3 repo. Expected: 20.2.4-1noble under debian-20.2.4/dists/noble/ and debian-tentacle/dists/noble/, matching 20.2.1 and 20.2.2. Questions: 1. Was noble coverage dropped after 20.2.2, or is this a break in the release/publishing pipeline? 2. If intentional, can this be documented and announced, given 20.2.1/20.2.2 already shipped noble? 3. Can noble packages be produced for 20.2.4 out-of-band, given the CVE severity and the "upgrade as soon as possible" guidance? Thanks, Homayoon Sadeghi