Project

General

Profile

Bug #21147

Manager daemon x is unresponsive. No standby daemons available

Added by Sage Weil almost 2 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Category:
-
Target version:
-
Start date:
08/27/2017
Due date:
% Done:

0%

Source:
Tags:
Backport:
luminous
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Pull request ID:

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.


Related issues

Copied to RADOS - Backport #22399: luminous: Manager daemon x is unresponsive. No standby daemons available Resolved

History

#1 Updated by Greg Farnum over 1 year ago

  • Status changed from Verified 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.

#2 Updated by Sage Weil over 1 year ago

  • Status changed from In Progress to Need Review

#3 Updated by Kefu Chai over 1 year ago

  • Status changed from Need Review to Pending Backport

#4 Updated by Nathan Cutler over 1 year ago

  • Copied to Backport #22399: luminous: Manager daemon x is unresponsive. No standby daemons available added

#5 Updated by Nathan Cutler over 1 year ago

  • Status changed from Pending Backport to Resolved

Also available in: Atom PDF