Dear Ceph Developers,
Earlier
today, I went to check one of the Telemetry commands in the Long
Running Cluster, and the command caused a crash in the mgr. The crash
was one that we had already seen during our testing of the Quincy RC,
and we had pushed a commit to fix it.
After
further investigation, I found that this commit, along with 4 other
commits, were not included in the v17.2.4 release when they should have
been.
These commits include:
- mgr/telemetry: handle daemons with complex id
- ceph-volume: fix regression in activate
- mgr/rook: fix error when trying to get the list of nfs services
- Revert "osd/PeeringState: proc_lease_ack break once found from OSD"
- Revert
"osd/PeeringState: fix missed `recheck_readable` from laggy"Adam King
also verified this by checking a 17.2.4 container, which proved to not
contain the above ceph-volume patch.
To
provide context, it was after Quincy RC was initially declared that we
upgraded the upstream clusters (Gibba and LRC) and found a handful of
regressions. We fixed these regressions with the above patches and added
them to the Quincy RC, which we verified again on our upstream
clusters.
Unfortunately,
due to a flaw in the release process, these last-minute patches were
not included in the v17.2.4 tag. What this means is that v17.2.4 is
currently based on an older Quincy RC version when it should be based on the latest version.
Here is a link to the latest Quincy RC branch, which should have been released as v17.2.4:
Here is a link to v17.2.4, which does not contain 5 important commits:
Here is a link to the diff between v17.2.4 and quincy-release. The commits shown should have been included in v17.2.4:
For
next steps, CLT members are currently evaluating the need for a hotfix
release. We are also reviewing our steps for the release process to
improve it for future releases. You can follow this email thread for updates
as we know more.
Please reach out to me, Neha, Vikhyat, Adam King, or Yuri for any questions.
Thanks,
Laura Flores
--
_______________________________________________
Dev mailing list -- dev@xxxxxxx
To unsubscribe send an email to dev-leave@xxxxxxx
