Thanks, this did work for me, (additionally I had to stop and restart the upgrade after stopping and restarting the first mgr manually, as it was in a failed no stdby mgr state), the cluster is now proceeding to updating the osds :) On 5/7/21 11:28 AM, Robert Sander wrote:
Am 07.05.21 um 10:42 schrieb Kai Börnert:
Hi, thanks for your explanation.
I see the 16.2.3 build is published, but (of course) I cannot update to it, as the version I currently use does still have this bug.
Is there some workaround/hack I can use to upgrade? I had success with stopping the "looping" mgr container via "systemctl stop" on the node. Cephadm then switches to another MGR to continue the upgrade. After that I just started the stopped mgr container and the upgrade continued.
Regards
_______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io