Project

General

Profile

Bug #44825

cephadm: bootstrap is not idempotent

Added by Patrick Donnelly 10 months ago. Updated 9 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
cephadm (binary)
Target version:
% Done:

0%

Source:
Tags:
Backport:
octopus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature:

Description

It would be helpful if this command did nothing if the cluster is already bootstrapped. This would simplify ansible rules for deployment.


Related issues

Related to Orchestrator - Bug #44824: cephadm: adding osd device is not idempotent New

History

#1 Updated by Sebastian Wagner 10 months 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.

#2 Updated by Sebastian Wagner 9 months ago

  • Related to Bug #44824: cephadm: adding osd device is not idempotent added

Also available in: Atom PDF