You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 20, 2024. It is now read-only.
From time to time we observe that bridge set up seems to have half-completed, so the initialization won't get run again on restart but it isn't properly set up.
Especially in a Kubernetes context this is hard to repair, and a reboot is generally easiest.
So this issue is to have some way to re-run the initialisation when needed.
The text was updated successfully, but these errors were encountered:
I'm deploying on a small cluster (6 nodes: 3 small controllers, 3 workers). If I reboot the machines, it seems there is no more network connection to anywhere, but if I delete everything, reboot again and redeploy, it works again.
Is this related?
(k8s: 1.7.4, weave 2.0.4, etcd. 3.2.6, docker 17.06.1, ...)
From time to time we observe that bridge set up seems to have half-completed, so the initialization won't get run again on restart but it isn't properly set up.
Especially in a Kubernetes context this is hard to repair, and a reboot is generally easiest.
So this issue is to have some way to re-run the initialisation when needed.
The text was updated successfully, but these errors were encountered: