Bug #57290
closedorch/cephadm: task/test_cephadm failure due to: ERROR: A cluster with the same fsid '00000000-0000-0000-0000-0000deadbeef' already exists.
0%
Description
This one I've actually been able to reproduce locally by running the test script. It seems that the shell command the script creates before bootstrapping creates the /var/lib/ceph/00000000-0000-0000-0000-0000deadbeef directory. Bootstrap sees this directory and then refuses to continue bootstrap as it believes a cluster with that fsid already exists. The problem is fairly straightforward and should be easy to fix, although I'm a bit confused as to why it's suddenly popping up now. Perhaps it only occurs on certain distros? The run that saw this and the env where I reproduced were both centos 8 stream and before these runs I think before including https://github.com/ceph/ceph/pull/47674 all these tests were being run on ubuntu.
https://pulpito.ceph.com/adking-2022-08-24_13:29:10-orch:cephadm-wip-adk-main-testing-2022-08-24-0725-distro-default-smithi/6988985
https://pulpito.ceph.com/adking-2022-08-22_22:45:20-orch:cephadm-wip-adk-testing-2022-08-22-1606-distro-default-smithi/6986559
Updated by Nitzan Mordechai over 1 year ago
/a/yuriw-2022-09-01_00:21:36-rados-wip-yuri7-testing-2022-08-31-0841-distro-default-smithi/7003410
Updated by Adam King over 1 year ago
- Status changed from In Progress to Pending Backport
- Backport set to quincy, pacific
- Pull request ID set to 47796
Updated by Backport Bot over 1 year ago
- Copied to Backport #57397: quincy: orch/cephadm: task/test_cephadm failure due to: ERROR: A cluster with the same fsid '00000000-0000-0000-0000-0000deadbeef' already exists. added
Updated by Backport Bot over 1 year ago
- Copied to Backport #57398: pacific: orch/cephadm: task/test_cephadm failure due to: ERROR: A cluster with the same fsid '00000000-0000-0000-0000-0000deadbeef' already exists. added
Updated by Laura Flores over 1 year ago
/a/yuriw-2022-09-07_00:05:42-rados-wip-yuri6-testing-2022-09-06-1353-quincy-distro-default-smithi/7016929
Updated by Adam King over 1 year ago
- Status changed from Pending Backport to Resolved