[Bug 2119024] Please test proposed package
Guillaume Boutry
2119024 at bugs.launchpad.net
Wed Nov 26 08:26:29 UTC 2025
Hello Ponnuvel, or anyone else affected,
Accepted ceph into caracal-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
sudo add-apt-repository cloud-archive:caracal-proposed
sudo apt-get update
Your feedback will aid us getting this update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-caracal-needed to verification-caracal-done. If it
does not fix the bug for you, please add a comment stating that, and
change the tag to verification-caracal-failed. In either case, details
of your testing will help us make a better decision.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!
** Changed in: cloud-archive/caracal
Status: New => Fix Committed
** Tags added: verification-caracal-needed
--
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/2119024
Title:
[SRU] Squid: Ceph new point release 19.2.3
Status in Ubuntu Cloud Archive:
New
Status in Ubuntu Cloud Archive caracal series:
Fix Committed
Status in ceph package in Ubuntu:
Fix Released
Status in ceph source package in Noble:
Fix Committed
Status in ceph source package in Plucky:
Fix Committed
Status in ceph source package in Questing:
Fix Committed
Status in ceph source package in Resolute:
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.2 https://ceph.io/en/news/blog/2025/v19-2-2-squid-released/
* ceph 19.2.3 https://ceph.io/en/news/blog/2025/v19-2-3-squid-released/
Notable changes:
* This fixes a silent RGW data loss regression when CopyObject is used to copy an object onto itself. The regression results in objects past the original 4mb head object being added to the garbage collection queue and deleted permanently, and are not recoverable.
* LTTNG has been enabled for easier tracing and debugging.
Key differences from upstream:
* libnbd has been disabled from the build system. libnbd is in universe in Ubuntu, and cannot be a dependency for 19.2.3.
* On questing, adjustments had to be made to build with boost1.88. On plucky and noble, these adjustments have been removed to build with standard boost 1.83 and 1.82.
* python-cryptography uses PyO3 to call some rust based bcrypt and TLS functions, and has problems being called in parallel and in sub-interpreters, necessary for ceph-dashboard to work correctly. This was fixed by backporting:
commit 717d0a6f3530ad3e07f4423002810327b2addcf1
From: "Paulo E. Castro" <pecastro at wormholenet.com>
Date: Sat, 5 Apr 2025 21:47:55 +0100
Subject: pybind/mgr: Hack around the 'ImportError: PyO3 modules
may only be initialized once per interpreter process' issue.
Link: https://github.com/ceph/ceph/commit/7094a5a44d90e705141dbae9739e6c0835bf7ce3
See also:
https://tracker.ceph.com/issues/64213
https://github.com/bazaah/aur-ceph/issues/20
https://bugs.launchpad.net/charm-ceph-dashboard/+bug/2073115
* Noble also receives the bugfix for hardened CFLAGS for python modules. See https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/2078244
[Test Case]
This SRU will run all functional tests with the packages in 'proposed'
for every Ceph charm maintained by Canonical's Ceph team, so that
there's a higher chance of catching bugs associated with any Ceph
component.
The charms for which the functional tests will be run are: ceph-mon, ceph-osd,
ceph-radosgw, ceph-proxy, ceph-nfs, ceph-nvme, ceph-fs and ceph-rbd-mirror.
The functional test suite includes upgrade testing from the current stable
release to the proposed (in this case, from 19.2.1 to 19.2.3)
Since our functional tests do not include testing for LTTNG, this will be
tested manually. This involves the following steps:
- Deploy a Ceph cluster with 19.2.3.
- Enable OSD tracing by adding the option `osd_tracing` to /etc/ceph.conf
- Run `lttng create test`
- Run `lttng enable-event --userspace osd:*`
- At this point, tracing is enabled. Do some writes to an OSD, e.g: By creating an RBD object or via ceph bench.
- Stop tracing with `lttng stop`
- View the logs with `lttng view`.
- We can then do some more writes on an OSD and verify that no more tracing output is generated.
[Regression Potential]
ceph is a critical package as it underpins large scale data storage
and integrity checking, and care must be taken to not introduce any
data loss regressions. ceph also is a common backing store for
OpenStack virtual machines through ceph-rbd, and care must be taken to
not break any API or ABI compatibility with current OpenStack
releases.
In order to mitigate the regression potential, the results of the
aforementioned tests will be attached to this bug.
[Other info]
Microrelease exception:
https://documentation.ubuntu.com/project/SRU/reference/exception-
OpenStack-Updates/
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/2119024/+subscriptions
More information about the Ubuntu-openstack-bugs
mailing list