ceph-crash "error connecting to the cluster" displayed in /var/log/messages

This document (000019763) is provided subject to the disclaimer at the end of this document.

Environment

Suse Enterprise Storage 6

Situation

The follwoing messages are displayed in /var/log/messages:
Oct 27 05:22:46 osd001 ceph-crash[5048]: WARNING:__main__:post /var/lib/ceph/crash/2020-10-26_17:31:09.957249Z_bb6ac037-41b6-4ead-a44c-3860cde6b8fe as client.crash failed: b'[errno 2] error connecting to the cluster\n'
Oct 27 05:22:46 osd001 ceph-crash[5048]: WARNING:__main__:post /var/lib/ceph/crash/2020-10-26_17:31:09.957249Z_bb6ac037-41b6-4ead-a44c-3860cde6b8fe as client.admin failed: b'[errno 2] error connecting to the cluster\n'

Resolution

Issue is resolved with deepsea version 0.9.31.

# rpm -qa | grep deepsea
deepsea-0.9.32+git.0.b6e716e76-3.24.1.noarch
deepsea-cli-0.9.32+git.0.b6e716e76-3.24.1.noarch
# rpm -q --changelog deepsea | grep 1174004
- Create and distribute keyring for ceph-crash (bsc#1174004)

To update deepsea, on the admin node run:
salt-run state.orch ceph.stage.0

Followed by:
salt-run state.orch ceph.stage.2
salt-run state.orch ceph.stage.3

Stage.3 will create "ceph.client.crash.keyring" and distribute to all the nodes in the cluster

Cause

"ceph.client.crash.keyring" is missing on all cluster nodes.

Status

Top Issue

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.