Actions
Bug #46230
closedfront_addr and cluster_network leads to hanging MGR
Status:
Won't Fix
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Regression:
No
Severity:
2 - major
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Since a day or so - all ceph orch commands are failing (although all other ceph commands run fine)
even after enabling debug_mgr = 5, the only entry in the mgr log is:
2020-06-26T12:19:40.608+0000 7fd53ae0c700 0 log_channel(audit) log [DBG] : from='client.994212 -' entity='client.admin' cmd=[{"prefix": "orch status", "target": ["mon-mgr", ""]}]: dispatch
Files
Actions
#3
Updated by Michal Nasiadka almost 4 years ago
- File ceph-mgr.strace ceph-mgr.strace added
- File ceph-mgr-3.log ceph-mgr-3.log added
Updated by Michal Nasiadka almost 4 years ago
- File config-key.dump config-key.dump added
Updated by Michal Nasiadka almost 4 years ago
Actually I noticed that some of my OSDs have front_addr in cluster_network - which is not accessible from Ceph monitors.
simple restart of those OSDs did help - and they have front_addr back in public_network - and everything started to work again.
Updated by Sebastian Wagner almost 4 years ago
- Related to Feature #46238: raise a HEALTH warn, if OSDs use the cluster_network for the front added
Updated by Sebastian Wagner almost 4 years ago
- Project changed from Orchestrator to mgr
- Subject changed from ceph orch commands hang forever to front_addr and cluster_network leads to hanging MGR
- Category deleted (
orchestrator)
Updated by Josh Durgin almost 4 years ago
- Status changed from New to Won't Fix
Sounds like this was a network configuration issue.
Actions