Bug #44694
MON_DOWN during cluster setup
Status:
Duplicate
Priority:
High
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Periodically tests see a MON_DOWN while the cluster is being built. This is presumably because the mons just aren't starting up at the exact same time?
Recent example:
/a/sage-2020-03-19_17:25:48-rados-wip-sage-testing-2020-03-19-0855-distro-basic-smithi/4868506
description: rados/singleton/{all/ec-lost-unfound.yaml mon_election/connectivity.yaml
msgr-failures/few.yaml msgr/async-v1only.yaml objectstore/bluestore-comp-snappy.yaml
rados.yaml supported-random-distro$/{ubuntu_latest.yaml}}
Related issues
History
#1 Updated by Neha Ojha almost 3 years ago
- Status changed from New to Duplicate
https://tracker.ceph.com/issues/45441 seems to be same issue.
#2 Updated by Neha Ojha almost 3 years ago
- Duplicates Bug #45441: rados: Health check failed: 1/3 mons down, quorum a,c (MON_DOWN)" in cluster log' added