https://bugzilla.suse.com/show_bug.cgi?id=1197490 https://bugzilla.suse.com/show_bug.cgi?id=1197490#c31 Fabian Vogt <fvogt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(rombert@apache.or | |g) --- Comment #31 from Fabian Vogt <fvogt@suse.com> --- (In reply to Robert Munteanu from comment #30)

(In reply to Fabian Vogt from comment #29)

...

That looks like the used CNI plugin is still the old broken one. Did the weave-init container run and replace it?

I am not sure about replacing it. Initially the output from the weave-init container is

modprobe: can't load module ip_set (kernel/net/netfilter/ipset/ip_set.ko.zst): invalid module format Ignore the error if "xt_set" is built-in in the kernel

I restarted all pods in the weave daemonset, but that did not help. There is no more output from the weave-init container, but the containers are still stuck in the ContainerCreating status.

FWICT, weave-init does if [ ! -f "$1/$CNI_PLUGIN_NAME" ]; then cp /usr/bin/weaveutil "$1/$CNI_PLUGIN_NAME" fi so it doesn't overwrite an existing cni plugin. You can try rm /opt/cni/bin/weave* and restarting weave-init. -- You are receiving this mail because: You are the assignee for the bug.