Bug #44673: cephadm: `orch apply` and `orch daemon add` use completely different code path - Orchestrator - Ceph

Actions

Copy link

Bug #44673

closed

cephadm: `orch apply` and `orch daemon add` use completely different code path

Added by Sebastian Wagner about 4 years ago. Updated about 3 years ago.

Status:

Rejected

Priority:

Normal

Assignee:

Category:

cephadm

Target version:

% Done:

Source:

Tags:

Backport:

Regression:

Severity:

3 - minor

Reviewed:

Affected Versions:

ceph-qa-suite:

Pull request ID:

35064

Crash signature (v1):

Crash signature (v2):

Description

... which is not obvious to users and they will use this interchangeably. Which is not really a good idea.

We should make it clear, that the CLI for doing unmanaged changes clearly states this.

Especially: cephadm will remove daemons added by daemon add!

Actions

Copy link

Updated by Sebastian Wagner about 4 years ago

Assignee set to Sage Weil

Actions

Copy link

Updated by Sage Weil about 4 years ago

Priority changed from High to Normal

Actions

Copy link

Updated by Sebastian Wagner about 4 years ago

I'm already getting bug reports, like

I just deployed a v15.2.0 cluster and ceph orch ls tells me 3 out of 0 mons are running - is that a known bug? 
master:~ # ceph orch ls
NAME                  RUNNING  REFRESHED  AGE   PLACEMENT          IMAGE NAME                                                               IMAGE ID      
mgr                       3/3  26s ago    103m  node1,node2,node3  registry.suse.de/devel/storage/7.0/cr/containers/ses/7/ceph/ceph:latest  4947e2bbb809  
mon                       3/0  26s ago    -     <no spec>          registry.suse.de/devel/storage/7.0/cr/containers/ses/7/ceph/ceph:latest  4947e2bbb809  
...

ah, maybe because the MONs are deployed using ceph orch daemon add mon and not ceph orch apply

Actions

Copy link