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.
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!
- Assignee set to Sage Weil
- Priority changed from High to Normal
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
- Assignee deleted (
Sage Weil)
- Status changed from New to Fix Under Review
- Pull request ID set to 35064
- Description updated (diff)
- Status changed from Fix Under Review to Rejected
Also available in: Atom
PDF