[Bug 2097605] Re: [SRU] Squid: Ceph new point release 19.2.1
Heitor Alves de Siqueira
2097605 at bugs.launchpad.net
Thu Jun 26 19:59:43 UTC 2025
Hi Luciano,
I've noticed that the verification for Oracular has been done against
the builds from your PPA. Unfortunately, for SRU purposes this must be
done with packages from proposed. I'm setting the tags back, and would
appreciate it if we could rerun validation against the current packages
from oracular-proposed.
Additionally, the testing from comment #14 seem rather light for Ceph. A
single-node cluster with a loop device would probably not catch the
regression we spotted in Noble, or any more impactful issues. Would you
be able to think of a test scenario for Oracular that would better
exercise the package? (maybe using NFS, or at least multiple nodes).
Thanks again for all the effort in helping with this Ceph release!
** Tags removed: verification-done-oracular
** Tags added: verification-needed-oracular
--
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to ceph in Ubuntu.
https://bugs.launchpad.net/bugs/2097605
Title:
[SRU] Squid: Ceph new point release 19.2.1
Status in Ubuntu Cloud Archive:
Triaged
Status in Ubuntu Cloud Archive caracal series:
Incomplete
Status in ceph package in Ubuntu:
Fix Released
Status in ceph source package in Noble:
Fix Committed
Status in ceph source package in Oracular:
Fix Committed
Status in ceph source package in Plucky:
Fix Released
Bug description:
[Impact]
This release fixes several bugs. We would like to make sure all of our
users have access to these improvements.
The update contains the following package updates:
* ceph 19.2.1
See https://docs.ceph.com/en/latest/releases/squid/#v19-2-1-squid for
release notes. Given it's a minor version update, there are no
backward-incompat. changes.
[Test Case]
The following SRU process was followed:
https://wiki.ubuntu.com/OpenStackUpdates
In order to avoid regression of existing users, the OpenStack team
will run their continuous integration test against the packages that
are in -proposed. A successful run of all available tests will be
required before the proposed packages can be let into -updates.
The OpenStack team will be in charge of attaching the output summary
of the executed tests. The OpenStack team members will not mark
‘verification-done’ until this has happened.
[Regression Potential]
In order to mitigate the regression potential, the results of the
aforementioned tests will be attached to this bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/2097605/+subscriptions
More information about the Ubuntu-openstack-bugs
mailing list