Actions
Bug #21147
closedManager daemon x is unresponsive. No standby daemons available
% Done:
0%
Source:
Tags:
Backport:
luminous
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
/a/sage-2017-08-26_20:38:41-rados-luminous-distro-basic-smithi/1567938
The last time I looked this appeared to be the mgr monc failing to reconnect quickly enough to get its beacon through. Need to review the last few failures and confirm that is the case.
Note that this error is whitelisted in a few places.
Updated by Greg Farnum over 6 years ago
- Status changed from 12 to In Progress
Sage believes this is due to high failure injections in the messenger in some of our testing, which makes it sometimes fail multiple times in a row until we exceed our timeout. He's putting a log whitelist in those yaml fragments.
Updated by Sage Weil over 6 years ago
- Status changed from In Progress to Fix Under Review
Updated by Kefu Chai over 6 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler over 6 years ago
- Copied to Backport #22399: luminous: Manager daemon x is unresponsive. No standby daemons available added
Updated by Nathan Cutler about 6 years ago
- Status changed from Pending Backport to Resolved
Actions