[Bug 2100625] Re: [SRU] ceph 17.2.9

[Chris Halse Rogers]

>> Does the exporter module work, and what is the testcase?

> It's meant to expose performance counters via the Prometheus endpoint.
We have tested that this works via the PPA, yes.

Could you please update the SRU test case to include testing this?
Testing should ensure the user-visible behaviour is fixed (ie: that the
daemon perf counters are exposed) rather than an implementation detail.

>> Does the Security Team know we are using the vendored boost library
instead of the distro packaged one?

> We haven't notified them of this. Since Ceph vendors in the same
libraries that are shipped with our distros, we didn't think it was
necessary.

We should certainly notify security that a new parser library is being
used; they will need to be able to track any CVEs it receives. This
might require packaging changes, I'm not sure what process they will
request.

-- 
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:
  In Progress

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