Closed Darwiner closed 6 years ago
@Darwiner, I can confirm that the check currently doesn't fully support ceph 12.2.1 (luminous). We have a task on the backlog for this and will update this issue once a PR is merged.
@jeremy-lq Actually, FWIW, I just stumbled onto this...
http://lists.ceph.com/pipermail/ceph-users-ceph.com/2017-September/021011.html
It would seem that in luminous, the new "appropriate" field to use for obtaining cluster status is "status" instead of "overall_status", and that "overall_status" returning HEALTH_WARN is their way to get people to stop using that field.
At least, that's what I make of the answer...
Output of the info page
Additional environment details (Operating System, Cloud provider, etc):
It would seem the current ceph service check might not support ceph 12.2.1 (luminous) yet?
Steps to reproduce the issue:
ceph -s
gives this output:Describe the results you received:
Yet, in the UI, or monitoring pages, these hosts are reporting ceph as being in a warning state as far as the
ceph.overall_status
service check is concerned...Considering the output of
ceph -s
has changed since the previous versions, I'm supposing there are some changes required to catch the correct status in this new version of ceph.Describe the results you expected:
Monitoring should report that the cluster state is OK.
Additional information you deem important (e.g. issue happens only occasionally):