Project

General

Profile

Actions

Bug #49510

closed

qa: file system deletion not complete because starter fs already destroyed

Added by Patrick Donnelly about 3 years ago. Updated almost 3 years ago.

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

0%

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

Description

During cleanup of ceph, the file systems are not cleaned up which causes unnecessary MDS failover messages:

2021-02-26T13:19:02.521 DEBUG:tasks.cephfs.filesystem:already dead...
...
2021-02-26T13:19:46.979 INFO:teuthology.orchestra.run.smithi138.stdout:2021-02-26T13:19:18.871401+0000 mon.a (mon.0) 498 : cluster [WRN] Replacing daemon mds.c as rank 0 with standby daemon mds.d

From: /ceph/teuthology-archive/pdonnell-2021-02-26_05:55:31-fs-wip-pdonnell-testing-20210226.035303-distro-basic-smithi/5916027/teuthology.log

The "starter" file system was already deleted by the cephfs task runner so when the ceph task tries to clean that up, it says the fs is already dead.

Make the cephfs task runner delete all file systems during tearDown.


Related issues 3 (0 open3 closed)

Copied to CephFS - Backport #49560: octopus: qa: file system deletion not complete because starter fs already destroyedResolvedNathan CutlerActions
Copied to CephFS - Backport #49561: pacific: qa: file system deletion not complete because starter fs already destroyedResolvedPatrick DonnellyActions
Copied to CephFS - Backport #49562: nautilus: qa: file system deletion not complete because starter fs already destroyedResolvedNathan CutlerActions
Actions

Also available in: Atom PDF