Actions
Bug #45726
closedModule 'cephadm' has failed: auth get failed: failed to find client.crash.<node_name> in keyring
Status:
Resolved
Priority:
Normal
Assignee:
Category:
cephadm
Target version:
% Done:
0%
Source:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Tags (freeform):
Merge Commit:
Fixed In:
v16.0.0-2917-g37d1815f9a
Released In:
v16.2.0~2164
Upkeep Timestamp:
2025-07-14T19:42:46+00:00
Description
[ceph: root@ceph-node-00 /]# ceph -s
cluster:
id: 8dc6f04a-9fee-11ea-a46a-525400622549
health: HEALTH_ERR
Module 'cephadm' has failed: auth get failed: failed to find client.crash.ceph-node-00 in keyring
....
Files
Updated by Juan Miguel Olmo Martínez almost 6 years ago
- Pull request ID set to 35274
Updated by Juan Miguel Olmo Martínez almost 6 years ago
Error lines related to this issue can be found in line 660 and next.
Updated by Sebastian Wagner almost 6 years ago
- Status changed from New to Fix Under Review
Updated by Andy Gold over 5 years ago
Any news on this, I have a new 15.2.4 cluster and its failing.
Updated by Sathvik Vutukuri over 5 years ago
Andy Gold wrote:
Any news on this, I have a new 15.2.4 cluster and its failing.
Any update no this , i also have similar issue.
Updated by Andy Gold over 5 years ago
Can we get the Priority set to something higher please.
Its not affecting the cluster, but it does cause the cluster to report RED and not healthy.
Updated by Sebastian Wagner over 5 years ago
- Status changed from Fix Under Review to Resolved
- Target version set to v15.2.5
Updated by Upkeep Bot 8 months ago
- Merge Commit set to 37d1815f9a2f535c982d6efdf1d06e24529da239
- Fixed In set to v16.0.0-2917-g37d1815f9a
- Released In set to v16.2.0~2164
- Upkeep Timestamp set to 2025-07-14T19:42:46+00:00
Actions