Bug #44825
closed
cephadm: bootstrap is not idempotent
Added by Patrick Donnelly about 4 years ago.
Updated about 2 years ago.
Category:
cephadm (binary)
Description
It would be helpful if this command did nothing if the cluster is already bootstrapped. This would simplify ansible rules for deployment.
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.
- Related to Bug #44824: cephadm: adding osd device is not idempotent added
- Related to Bug #45909: already existing cluster deployed: cephadm bootstrap failure added
- Priority changed from Normal to Low
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.
- Status changed from New to Rejected
Also available in: Atom
PDF