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

[Heitor Alves de Siqueira]

Thanks, Luciano! I've grabbed the relevant patch, and sponsored the
follow-up fix for the version that's currently in noble-proposed.

For the SRU team: based on prior discussions in this bug (comments #15
to #19), we're requesting the "pushing ahead" scenario of [0]. Andreas
has hinted that this would be OK in those comments, but I wanted to be
explicit about this in a follow-up comment. This seems to be a fairly
reasonable case: the regression has been identified, the fix is very
simple and has been tested/validated by the Ceph Engineering team.
Considering this is also a point release upload, reverting the current
package in proposed seems undesired.

If there are any issues with this approach, please feel free to drop the
follow-up from the Noble upload queue.

[0] https://documentation.ubuntu.com/sru/en/latest/explanation/standard-
processes/#explanation-regressions

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