Hi Wesley,
I can only answer your second question and give an opinion on the last one!
- Yes the OSD activation problem (in cephadm clusters only) was
introduce by an unfortunate change (indentation problem in Python code)
in 16.2.11. The issue doesn't exist in 16.2.10 and is one of the fixed
A few questions:
- Will the 16.2.12 packages be "corrected" and reuploaded to the ceph.com
mirror? or will 16.2.13 become what 16.2.12 was supposed to be?
- Was the osd activation regression introduced in 16.2.11 (or does 16.2.10
have it as well)?
- Were the hotfxes in 16.2.12 just related to
Dear List
we upgraded to 16.2.12 on April 17th, since then we've seen some
unexplained downed osd services in our cluster (264 osds), is there any
risk of data loss, if so, would it be possible to downgrade or is a fix
expected soon? if so, when? ;-)
FYI, we are running a cluster without
We are writing to inform you that Pacific v16.2.12, released on April
14th, has many unintended commits in the changelog than listed in the
release notes [1].
As these extra commits are not fully tested, we request that all users
please refrain from upgrading to v16.2.12 at this time. The current
