Project

General

Profile

Bug #47202

qa: Replacing daemon mds.a as rank 0 with standby daemon mds.b" in cluster log

Added by Patrick Donnelly 5 months ago. Updated 3 months ago.

Status:
Resolved
Priority:
Normal
Category:
-
Target version:
% Done:

0%

Source:
Q/A
Tags:
Backport:
octopus,nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
qa-suite
Labels (FS):
Pull request ID:
Crash signature:

Description

Failure: "2020-08-24T22:22:39.819658+0000 mon.a (mon.0) 381 : cluster [WRN] Replacing daemon mds.a as rank 0 with standby daemon mds.b" in cluster log
1 jobs: ['5372952']
suites: ['clusters/1-mds-4-client-coloc', 'conf/{client', 'fs/basic_functional/{begin', 'mds', 'mon', 'mount/fuse', 'no_client_pidfile', 'objectstore/bluestore-bitmap', 'osd}', 'overrides/{frag_enable', 'supported-random-distros$/{rhel_8}', 'tasks/cap-flush}', 'whitelist_health', 'whitelist_wrongly_marked_down}']

From: /ceph/teuthology-archive/pdonnell-2020-08-24_21:54:31-fs-wip-pdonnell-testing-20200824.202017-distro-basic-smithi/5372952/teuthology.log


Related issues

Copied to CephFS - Backport #47246: nautilus: qa: Replacing daemon mds.a as rank 0 with standby daemon mds.b" in cluster log Resolved
Copied to CephFS - Backport #47247: octopus: qa: Replacing daemon mds.a as rank 0 with standby daemon mds.b" in cluster log Resolved

History

#1 Updated by Patrick Donnelly 5 months ago

  • Status changed from In Progress to Fix Under Review
  • Pull request ID set to 36887

#2 Updated by Patrick Donnelly 5 months ago

  • Status changed from Fix Under Review to Pending Backport

#3 Updated by Nathan Cutler 5 months ago

  • Copied to Backport #47246: nautilus: qa: Replacing daemon mds.a as rank 0 with standby daemon mds.b" in cluster log added

#4 Updated by Nathan Cutler 5 months ago

  • Copied to Backport #47247: octopus: qa: Replacing daemon mds.a as rank 0 with standby daemon mds.b" in cluster log added

#5 Updated by Nathan Cutler 3 months ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Also available in: Atom PDF