6 May
2021
6 May
'21
2:57 p.m.
Hi all, upon updating to 16.2.2 via cephadm the upgrade is being stuck on the first mgr Looking into this via docker logs I see that it is still loading modules when it is apparently terminated and restarted in a loop When pausing the update, the mgr succeeds to start with the new version, however when resuming the update, it seems to try to update it again even tho it already has the new version, leading to the exact same loop. Is there some setting or workaround to increase the time before it is attempted to be redeployed, or can this behavior be caused by something else? Greetings, Kai