Hi,
Yes! I did play with another cluster before and forgot to completely
clear that node! And the fsid "46e2b13c-dab7-11eb-810b-a5ea707f1ea1"
from that cluster. But then there is an error in CEPH. Because the
mon the existing cluster complained about (with fsid
"1ef45b26-dbac-11eb-a357-616c355f48cb") was also from the old
cluster, with fsid "46e2b13c-dab7-11eb-810b-a5ea707f1ea1".
then you should check your orch placement for the mon service. Maybe
cephadm picked it in an earlier state? Have you checked your current
specs?
ceph orch ls --export --format yaml
Zitat von Fyodor Ustinov <ufm@xxxxxx>:
Hi!
no problem. Maybe you played around and had this node in the placement
section previously? Or did it have the mon label? I'm not sure, but
the important thing is that you can clean it up.
Yes! I did play with another cluster before and forgot to completely
clear that node! And the fsid "46e2b13c-dab7-11eb-810b-a5ea707f1ea1"
from that cluster. But then there is an error in CEPH. Because the
mon the existing cluster complained about (with fsid
"1ef45b26-dbac-11eb-a357-616c355f48cb") was also from the old
cluster, with fsid "46e2b13c-dab7-11eb-810b-a5ea707f1ea1".
WBR,
Fyodor.
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
