[Bug 2097605] Re: [SRU] Squid: Ceph new point release 19.2.1

[Luciano Lo Giudice]

Hello Andreas,

a)
> Why would you not have charms for oracular?

We (as in the Ceph team) never got around to it. This isn't restricted
to Ceph, however, as many charms that we rely on to do extensive testing
also do not support Oracular. For example, we use the Ubuntu charm for
the Ceph-FS tests, and it doesn't support Oracular (see:
https://charmhub.io/ubuntu which lacks support for 24.10); the Mysql-
Innodb-Cluster is in a similar situation, and it's used when testing
broad Openstack deployments (see: https://charmhub.io/mysql-innodb-
cluster).

Many other charms that we depend on do not support Oracular either,
which is why the alternative test plan was presented, something that
also happened during the 18.2.0 point release for Ceph on Mantic. This
alternative test plan was approved back then, and I assumed it was
deemed sufficient.

b) I'm not sure if this implies a verification failure. We need a re-
upload with a very small change for a specific patch that only applies
to noble. If that constitutes a failure, I can update the verification
tag.

-- 
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