Hi Yuri,

On Fri, Nov 21, 2025 at 4:34 AM Yuri Weinstein <[email protected]> wrote:
>
> Note:  this is an attempt to test and publish post EOL reef point release
>
> Details of this release are summarized here:
>
> https://tracker.ceph.com/issues/73906#note-1
> Release Notes - TBD
> LRC upgrade - N/A
>
> distro => jammy focal centos9 windows bookworm
>
> Seeking approvals/reviews for:
>
> smoke - Laura approved?
>
> rados - Radek, Laura approved? Travis?  Nizamudeen? Adam King approved?
> (rados is also running on build 2 == build 1 +
> https://github.com/ceph/ceph/pull/66056 per Igor's request)
>
> rgw - Adam E approved?
>
> fs - Venky approved?

There are lot many failures in the fs suite resembling

        Error mounting /var/lib/ceph: mount: /var/lib/ceph: wrong fs
type, bad option ...

which is an issue with the testing kernel. Adding Alex who was looking
into this issue.

As far as the run validation is concerned, it's risky to ignore the
large number of failures. We have two options:

- fix the testing kernel issue and rerun
- rerun with `for-linus` branch (with `-k for-linus` in the
teuthology-suite schedule command)

The latter would be using an older kernel branch, but I think it
should suffice for this case.

>
> orch - Adam King approved?
>
> rbd - Ilya approved?
> krbd - Ilya approved?
>
> upgrade/pacific-x (reef) - can this be deprecated?  Josh?  Neha? (same as
> in 18.2.5)
> upgrade/quincy-x (reef) - Laura, Prashant please take a look. (same as in
> 18.2.5)
>
> powercycle - Brad approved?
> ceph-volume - see orch, Guillaume approved?
>
> Notably upgrades suites show same results as for 18.2.5 (tested in March
> 2025)
>
> To compare, see 18.2.5 tests https://tracker.ceph.com/issues/70563#note-1
> TIA
> _______________________________________________
> ceph-users mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>


-- 
Cheers,
Venky
_______________________________________________
ceph-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to