That's very odd, I haven't seen this before. What container image is the upgraded mgr running on (to know for sure, can check the podman/docker run command at the end of the /var/lib/ceph/<fsid>/mgr.<mgr-id>/unit.run file on the mgr's host)? Also, could maybe try "ceph mgr module enable cephadm" to see if it does anything? On Tue, Mar 14, 2023 at 9:23 AM bbk <bbk@xxxxxxxxxx> wrote: > Dear List, > > Today i was sucessfully upgrading with cephadm from 16.2.8 -> 16.2.9 -> > 16.2.10 -> 16.2.11 > > Now i wanted to upgrade to 17.2.0 but after starting the upgrade with > > ``` > # ceph orch upgrade start --ceph-version 17.2.0 > ``` > > The orch manager module seems to be gone now and the upgrade don't seem to > run. > > > ``` > # ceph orch upgrade status > Error ENOENT: No orchestrator configured (try `ceph orch set backend`) > > # ceph orch set backend cephadm > Error ENOENT: Module not found > ``` > > During the failed upgrade all nodes had the 16.2.11 cephadm installed. > > Fortunately the cluster is still running... somehow. I installed the > latest 17.2.X cephadm on all > nodes and rebooted them nodes, but this didn't help. > > Does someone have a hint? > > Yours, > bbk > _______________________________________________ > ceph-users mailing list -- ceph-users@xxxxxxx > To unsubscribe send an email to ceph-users-leave@xxxxxxx > > _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |