Bug 2144435 - cephadm rm-cluster sometimes gets stuck with Lock <num> not acquired on /run/cephadm/<fsid>.lock
Summary: cephadm rm-cluster sometimes gets stuck with Lock <num> not acquired on /run/...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Cephadm
Version: 5.3
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 8.0
Assignee: Adam King
QA Contact: Manisha Saini
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-21 09:12 UTC by Vasishta
Modified: 2023-07-06 17:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 51671 0 None None None 2022-11-21 09:12:19 UTC
Red Hat Issue Tracker RHCEPH-5661 0 None None None 2022-11-21 09:29:07 UTC

Description Vasishta 2022-11-21 09:12:19 UTC 
Description of problem:
'cephadm rm-cluster --force' gets stuck sometimes

Version-Release number of selected component (if applicable):
cephadm-16.2.10-69.el8cp.noarch

How reproducible:
Could reproduce in 4 nodes of the same cluster

Steps to Reproduce:
1. Configure cluster and try to purge (Tried without cephadm-ansible)

Actual results:
2022-11-21 07:19:14,420 7fa4a0c50b80 DEBUG Acquiring lock 140344940079760 on /run/cephadm/28e06588-5bfa-11ed-8f8a-004e013d8491.lock
2022-11-21 07:19:14,420 7fa4a0c50b80 DEBUG Lock 140344940079760 not acquired on /run/cephadm/28e06588-5bfa-11ed-8f8a-004e013d8491.lock, waiting 0.05 seconds ...

Expected results:
rm-cluster not to get stuck

Additional info:
Workaround is to remove /run/cephadm/<fsid>.lock and try rm-cluster again.
Note You need to log in before you can comment on or make changes to this bug.