[Bug 2100625] Re: [SRU] ceph 17.2.9

[Luciano Lo Giudice]

I've run full test suite for Jammy using -proposed and everything went
well: https://github.com/canonical/ceph-charms/actions/runs/17949194746

To prove that the right ceph version was being used, I SSH'd into a
machine used in that model and ran:

ubuntu at juju-66eb0f-0:~$ apt-cache policy ceph
ceph:
  Installed: 17.2.9-0ubuntu0.22.04.1
  Candidate: 17.2.9-0ubuntu0.22.04.1
  Version table:
 *** 17.2.9-0ubuntu0.22.04.1 500
        500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     17.2.7-0ubuntu0.22.04.2 500
        500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
     17.1.0-0ubuntu3 500
        500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages

** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done-jammy

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

Title:
  [SRU] ceph 17.2.9

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive yoga series:
  Triaged
Status in ceph package in Ubuntu:
  Invalid
Status in ceph source package in Focal:
  Invalid
Status in ceph source package in Jammy:
  Fix Committed

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 17.2.9
     * Race condition prevention when printing Inode in ll_sync_inode (by Ponnuvel Palaniyappan)

  [Test Case]
  The following SRU process was followed:

  https://documentation.ubuntu.com/sru/en/latest/reference/exception-
  OpenStack-Updates/

  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/2100625/+subscriptions