Hi Team, Followed the mentioned procedure on NVME's and failed. Raised a bug for the same - https://bugzilla.redhat.com/show_bug.cgi?id=1954503 Once the bug is fixed please verify on NVME's. Regards, Bharath
@rmandyam : The problem in BZ 1954503 is about the use of FDQN name as hostnames in the cluster nodes. I want to raise this question with the dev. team (today). Because we have several options here that probably will imply changes in documentation. For example, one possibility is to ban the use of FQDN names in the cluster hosts... another can be just warn about the impossibility to reuse osds ids in hosts with FQDN naming schema, and even we have more options .... so lest see what is the better one. I will update today this bug with our decision.
(In reply to Juan Miguel Olmo from comment #10) > @rmandyam : > > The problem in BZ 1954503 is about the use of FDQN name as hostnames in the > cluster nodes. > > I want to raise this question with the dev. team (today). Because we have > several options here that probably will imply changes in documentation. > For example, one possibility is to ban the use of FQDN names in the cluster > hosts... another can be just warn about the impossibility to reuse osds ids > in hosts with FQDN naming schema, and even we have more options .... so lest > see what is the better one. > > I will update today this bug with our decision. Any update on the same ?
Need clarification to verify this issue.
As mentioned in the https://bugzilla.redhat.com/show_bug.cgi?id=1954503#c12, as a workaround using the bare names. If the user uses FQDN names then failing to delete OSD's. Need clarification that, is this issue is going to mention as a part of known issues?
The issue https://bugzilla.redhat.com/show_bug.cgi?id=1954503 is targeted to 5.1. Include the BZ #1954503 in 5.0 known issues. The workaround mentioned in "https://docs.ceph.com/en/latest/rados/operations/add-or-rm-osds/#removing-osds-manual " is working