Lock acquisition hangs with kubedock 0.14.0 about kubedock HOT 4 CLOSED

Thanks for the fast fix! I can confirm that the problem is resolved with 0.14.1.

from kubedock.

This seems like a comeback of #40. The Lease resource is again left with a non-empty holderIdentity field after kubedock terminates.

Starting fails with timeout acquiring lock right, and you do see exit signal recieved, removing pods, configmaps and services when kubedock stops?

It looks indeed like #40 is back.

from kubedock.

In #40 I did not found the root-cause, but re-organizing and rewriting the exit handler worked around it. Moving towards go 1.21 re-introduced the bug.

The root-cause is that the main go-routine is killed before the exit handler was finished, which would crash the exit handler. Making the main go-routine wait indefinitely and moving the exit responsibility to the exit handler (which was the initial imlementation/idea), makes sure all cancelations (including the release lock) are executed.

from kubedock.

Released https://github.com/joyrex2001/kubedock/releases/tag/0.14.1 with this fix.

from kubedock.