Project

General

Profile

Actions

Bug #51671

closed

cephadm rm-cluster stuck: No indication that /run/cephadm/<fsid>.lock was never cleaned up

Added by Sebastian Wagner almost 3 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
Normal
Category:
cephadm (binary)
Target version:
-
% Done:

0%

Source:
Tags:
ux low-hanging-fruit good-first-issue
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

rm-cluster, it seemed to hang forever until I removed /run/cephadm/<fsid>.lock (and the cephadm.log was quickly flooding with retries grabbing that lock).

https://github.com/ceph/ceph/blob/ac001cbd2ee154be98108cd1d1277fb73037eda5/src/cephadm/cephadm#L1165

It's already prited into the log file, but no one is looking at it. So, we also have to print it to stderr

Actions #1

Updated by Sebastian Wagner almost 3 years ago

  • Description updated (diff)
Actions #2

Updated by Varsha Rao almost 3 years ago

  • Tags changed from ux low-hanging-fruit to ux low-hanging-fruit good-first-issue
Actions #3

Updated by Redouane Kachach Elhichou about 2 years ago

  • Status changed from New to In Progress
  • Assignee set to Redouane Kachach Elhichou
Actions #4

Updated by Redouane Kachach Elhichou about 2 years ago

  • Status changed from In Progress to Fix Under Review
  • Pull request ID set to 45931
Actions #5

Updated by Redouane Kachach Elhichou almost 2 years ago

since we now have support to handle logging properly for interactive operations (such as bootstrap, rm-cluster, etc) we can see warning logs in stderr.

Actions #6

Updated by Redouane Kachach Elhichou almost 2 years ago

  • Status changed from Fix Under Review to Resolved
Actions

Also available in: Atom PDF