It comes from this backport (https://github.com/ceph/ceph/pull/56713) that made it to 17.2.8 but was not in 18.2.4, there is an extra argument that you need to remove from the mgr/cephadm/client_keyring to be able to proceed with the upgrade. This is an example below on how to hack it. # ceph config-key get "mgr/cephadm/client_keyrings" {"client.admin": {"entity": "client.admin", "placement": {"label": "_admin"}, "mode": 384, "uid": 0, "gid": 0, "include_ceph_conf": true}} # ceph config-key set "mgr/cephadm/client_keyrings" '{"client.admin": {"entity": "client.admin", "placement": {"label": "_admin"}, "mode": 384, "uid": 0, "gid": 0}}' set mgr/cephadm/client_keyrings # ceph config-key get "mgr/cephadm/client_keyrings" {"client.admin": {"entity": "client.admin", "placement": {"label": "_admin"}, "mode": 384, "uid": 0, "gid": 0}} https://tracker.ceph.com/issues/67660#note-4 Besides that the only other way to get out of this situation is to keep failing the mgr ` ceph mgr fail ` until you get the mgr that is 17.2.8 back as active to get the `ceph orch` commands back and stop the upgrade ` ceph orch upgrade stop`, but there is a short window to do this until it becomes unresponsive again. You find this error by looking at the journalctl of the 17.2.8 mgr. _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |