Re: [ceph-users] Re: reef 18.2.8 QE validation status
On Thu, Feb 19, 2026 at 9:00 PM Laura Flores via Dev <dev@ceph.io> wrote:
I reviewed the upgrade suites. There were some infrastructure problems that affected a significant number of the results, which I think we should get fixed before we approve the upgrades.
@David Galloway <david.galloway@ibm.com>, the main issue is that we are missing packages/containers for Quincy and Pacific. See details in https://tracker.ceph.com/issues/75034 <https://qcflzmq6.r.us-east-1.awstrack.me/L0/https:%2F%2Ftracker.ceph.com%2Fissues%2F75034/1/0100019c777d9e26-573a43dc-1e9b-4062-9de7-2559520fc0a5-000000/E8HF8NYI-pW4w0BgN7Se41EkWRA=466> .
The reef point-to-point tests did not have any infrastructure failures, but there were two new bugs that I raised for RBD and the Dashboard. @Ilya Dryomov <idryomov@ibm.com> and @afreen@ibm.com <afreen@ibm.com>, can you take a look?
*upgrade:quincy-x* 1. https://tracker.ceph.com/issues/75034 <https://qcflzmq6.r.us-east-1.awstrack.me/L0/https:%2F%2Ftracker.ceph.com%2Fissues%2F75034/2/0100019c777d9e26-573a43dc-1e9b-4062-9de7-2559520fc0a5-000000/UUcPCw7uyvIGAcxlWNntchK6v90=466> - Missing packages and container images in upgrade tests - (Infrastructure)
*upgrade:pacific-x* 1. https://tracker.ceph.com/issues/75034 <https://qcflzmq6.r.us-east-1.awstrack.me/L0/https:%2F%2Ftracker.ceph.com%2Fissues%2F75034/3/0100019c777d9e26-573a43dc-1e9b-4062-9de7-2559520fc0a5-000000/C76yMyOupDETiidC1BSvPFbLZ7M=466> - Missing packages and container images in upgrade tests - (Infrastructure)
*upgrade:reef-p2p* 1. https://tracker.ceph.com/issues/75037 <https://qcflzmq6.r.us-east-1.awstrack.me/L0/https:%2F%2Ftracker.ceph.com%2Fissues%2F75037/1/0100019c777d9e26-573a43dc-1e9b-4062-9de7-2559520fc0a5-000000/M0Ke643EdMp-5mkJt-o-qNYCgSE=466> - src/test/pybind/test_rbd.py::test_remove_canceled fails from coredump - (rbd)
Hi Laura, I think this is the same thing that I have noted in an earlier email in this thread:
[...] but the crashes in test_librbd_python.sh are concerning. Patrick and I discussed them briefly -- they seem to be specific to 20.04, but I don't remember seeing them before. There were multiple passes on 20.04 in the run that I approved last year [2], so it looks like something around Python, Cython or the build process has changed in the interim.
[1] https://pulpito.ceph.com/dis-2026-02-02_19:37:16-rbd-reef-release-distro-def... [2] https://pulpito.ceph.com/yuriw-2025-11-18_23:00:18-rbd-reef-release-distro-d...
-- Ilya
On Thu, Feb 19, 2026 at 9:39 PM Ilya Dryomov <idryomov@gmail.com> wrote:
On Thu, Feb 19, 2026 at 9:00 PM Laura Flores via Dev <dev@ceph.io> wrote:
I reviewed the upgrade suites. There were some infrastructure problems that affected a significant number of the results, which I think we should get fixed before we approve the upgrades.
@David Galloway, the main issue is that we are missing packages/containers for Quincy and Pacific. See details in https://tracker.ceph.com/issues/75034.
The reef point-to-point tests did not have any infrastructure failures, but there were two new bugs that I raised for RBD and the Dashboard. @Ilya Dryomov and @afreen@ibm.com, can you take a look?
upgrade:quincy-x 1. https://tracker.ceph.com/issues/75034 - Missing packages and container images in upgrade tests - (Infrastructure)
upgrade:pacific-x 1. https://tracker.ceph.com/issues/75034 - Missing packages and container images in upgrade tests - (Infrastructure)
upgrade:reef-p2p 1. https://tracker.ceph.com/issues/75037 - src/test/pybind/test_rbd.py::test_remove_canceled fails from coredump - (rbd)
Hi Laura,
I think this is the same thing that I have noted in an earlier email in this thread:
[...] but the crashes in test_librbd_python.sh are concerning. Patrick and I discussed them briefly -- they seem to be specific to 20.04, but I don't remember seeing them before. There were multiple passes on 20.04 in the run that I approved last year [2], so it looks like something around Python, Cython or the build process has changed in the interim.
[1] https://pulpito.ceph.com/dis-2026-02-02_19:37:16-rbd-reef-release-distro-def... [2] https://pulpito.ceph.com/yuriw-2025-11-18_23:00:18-rbd-reef-release-distro-d...
Sigh, I have wasted a good chunk of my day today only to figure out that it's Ubuntu's apport that is causing this. The tracker [1] has the details. I reran one of the failed test_librbd_python.sh jobs [2][3] with the Python exception hook forcefully reverted to default and it passed [4]. rbd is now approved. krbd was approved on Feb 6th. [1] https://tracker.ceph.com/issues/75037 [2] https://pulpito.ceph.com/yuriw-2026-01-27_16:01:10-rbd-reef-release-distro-d... [3] https://pulpito.ceph.com/dis-2026-02-02_19:37:16-rbd-reef-release-distro-def... [4] https://pulpito.ceph.com/dis-2026-02-20_20:17:31-rbd-reef-distro-default-tri... Thanks, Ilya
participants (1)
-
Ilya Dryomov