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

[Christian Rohmann]

Tyler I suppose you are referring to e.g.
https://lists.ceph.io/hyperkitty/list/ceph-
users at ceph.io/thread/IPHBE3DLW5ABCZHSNYOBUBSI3TLWVD22/ ?

Yes, mClock seems, also reading through the other recent posts, to be something operators have issues with.
Either with slow convergence (recovery), influence of scrubbing, ....


But considering the SRU / update from 17.2.6 to 17.2.7 those might also not be problems / regressions of this particular point release. All of 17.x (Quincy) is using mClock scheduler by default. I believe it's more about more installations moving to mClock that we now see more and more issues.

What I am trying to say is that 17.2.7 might actually not make things
any worse, but could actually deliver fixes / improvements that Ceph has
done.

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

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