rados-approved. Note that we did see one new failure, but we determined it to be an issue with our build environment. See details here: https://tracker.ceph.com/issues/71182. upgrade/quincy-x approved as well. On Mon, May 5, 2025 at 3:11 PM Ilya Dryomov <idryomov@gmail.com> wrote:
On Fri, May 2, 2025 at 2:03 AM Yuri Weinstein <yweinste@redhat.com> wrote:
Details of this release are summarized here:
https://tracker.ceph.com/issues/71166 Release Notes - https://github.com/ceph/ceph/pull/63090 LRC upgrade - N/A
Seeking approvals/reviews for:
smoke - same as in 18.2.5 rados - Laura, Mark N, Igor approved? upgrade/quincy-x (reef) - Laura approved? upgrade/reef-p2p - unexpected failure in `test_librbd_python.sh` Ilya PTL (it did pass in 18.2.5 https://tracker.ceph.com/issues/70563 and was not ran in 18.2.6)
Hi Yuri,
This is yet another instance of a general problem with upgrade suites where they hard-code branch names:
$ cat qa/suites/upgrade/reef-p2p/reef-p2p-stress-split/6-final-workload/rbd-python.yaml meta: - desc: | librbd python api tests tasks: - workunit: branch: reef <------ clients: client.0: - rbd/test_librbd_python.sh - print: "**** done rbd/test_librbd_python.sh 7-workload"
So even though you are scheduling the run on reef-release it still ends up using test definitions from reef against librbd from reef-release and various issues arise in case of mismatch (i.e. if something is merged in reef but not in reef-release). Here the mismatch is caused by [1].
Approving based on a rerun with a tweak to avoid the mismatch [2].
[1] https://github.com/ceph/ceph/pull/62967 [2] https://pulpito.ceph.com/dis-2025-05-05_16:31:07-upgrade:reef-p2p-reef-relea...
Thanks,
Ilya _______________________________________________ Dev mailing list -- dev@ceph.io To unsubscribe send an email to dev-leave@ceph.io
-- Laura Flores She/Her/Hers Software Engineer, Ceph Storage <https://ceph.io> Chicago, IL lflores@ibm.com | lflores@redhat.com <lflores@redhat.com> M: +17087388804