Node failed after add-node - "Error: missing content for serving cert" - front-proxy-client.crt is zero bytes

[gsnsw-felixs]

Summary

New node failed after adding to existing HA cluster (4 nodes) with error:

microk8s.daemon-kubelite[508516]: Error: missing content for serving cert "aggregator-proxy-cert::/var/snap/microk8s/3597/certs/front-proxy-client.crt::/var/snap/microk8s/3597/certs/front-proxy-client.key"

(Then a miliion Go stacktrace lines...)

In the certs folder:

/var/snap/microk8s/3597/certs/front-proxy-client.crt was 0 bytes.

Regenerated the cert with:

sudo microk8s refresh-certs -e front-proxy-client.crt

and then the kubelite service started correctly.

What Should Happen Instead?

The newly added node should not die, should report the cert error without excessively long stacktraces.

Reproduction Steps

This might have happened once before with this version, but I just deleted and re-created that time.

Introspection Report

Sorry, don't want to expose logs info.

Can you suggest a fix?

Check that certs were generated correctly before / during node add?

Are you interested in contributing with a fix?

no