Bug #44825
closedcephadm: bootstrap is not idempotent
0%
Description
It would be helpful if this command did nothing if the cluster is already bootstrapped. This would simplify ansible rules for deployment.
Updated by Sebastian Wagner about 4 years ago
Making cephadm bootstrap truly idempotent will not be trivial. As there are going to be some special cases, like: what about existing daemons that were not created by `cephadm bootstrap`
Please don't use --allow-overwrite:
cephadm bootstrap --allow-overwrite #WRONG!
which makes you able to call bootstrap multiple times, but does not remove the old cluster.
Updated by Sebastian Wagner about 4 years ago
- Related to Bug #44824: cephadm: adding osd device is not idempotent added
Updated by Sebastian Wagner about 4 years ago
ceph-salt as well: https://github.com/ceph/ceph-salt/issues/173
Updated by Sebastian Wagner almost 3 years ago
- Related to Bug #45909: already existing cluster deployed: cephadm bootstrap failure added
Updated by Sebastian Wagner over 2 years ago
- Priority changed from Normal to Low
Updated by Redouane Kachach Elhichou about 2 years ago
To be honest, I don't see the benefit of this feature-request. Bootstrap right now will fail if a cluster with the same id already exists. So user should delete the previous cluster before creating the new one (with the same id). I'm closing the issue. Please re-open if you think that this is still a useful feature that we have to consider for cephadm.
Updated by Redouane Kachach Elhichou about 2 years ago
- Status changed from New to Rejected