[Bug 2043336] Re: [SRU] ceph 17.2.7 point release

[Andreas Hasenack]

This upload contains some changes that are not mentioned here or in d/changelog:
- new file debian/ceph.patch. Not referenced anywhere, according to grep. Cruft?
- dropped CVE-2023-43040.patch, presumably upstream (confirmed in the changelog at https://docs.ceph.com/en/latest/releases/quincy/#v17-2-7-quincy), but not mentioned in d/changelog

Additionally, the d/p/fix-lvm-devices.patch could use better DEP3
headers, like an upstream reference, shown in comment #15 (and that PR
is merged now).

This last one is not a blocker, but the d/ceph.patch file needs some
explanation please.


** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-43040

** Changed in: ceph (Ubuntu Jammy)
       Status: Triaged => Incomplete

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

Title:
  [SRU] ceph 17.2.7 point release

Status in Ubuntu Cloud Archive:
  Triaged
Status in ceph package in Ubuntu:
  Invalid
Status in ceph source package in Jammy:
  Incomplete

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

  [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/2043336/+subscriptions