-
Notifications
You must be signed in to change notification settings - Fork 678
Weave NPC ipset failed: ipset v6.32: The set is full, more elements cannot be added #3289
Comments
Thanks for the issue. Indeed, the default size of an ipset of the list:set type is 8. We can change it by passing "size N" when creating the ipset. |
I tried this on a 4.13 kernel, and the set size doesn't seem so fixed:
|
From
So, we can assume that a set of the list:set type can grow dynamically since 6.24 (released 4 years ago). |
OK, so do we have any theories about the problem the OP reported? |
I've just checked with CentOS 7 (kernel 3.10), and the problem exists as reported. |
Thanks for your help. In our case its CentOS Linux release 7.4.1708 (Core) with kernel 3.10.0. ipset version is
but
|
Fixed by #3305 |
What you expected to happen?
I have the following kubernetes network policy:
I also have 10 (and more in the future) namespaces wich will match in this policy.
I expected this to work.
It worked as i reduced the number of namespaces to under 8. 8 is the default size of a ipset list, and the ipset here has
Header: size 8
setipset list
.I think weave does not set a size for the ipset list, and therfor it is created with the default of 8, and the npc dies when trying to add a ninth entry to the set.
What happened?
weave-npc dies with the following log entrys:
How to reproduce it?
Create more than 10 namespaces and use the networkpolicy above.
Versions:
$ weave version
2.3.0
$ docker version
$ uname -a
Linux zed-lmon-node1 3.10.0-693.21.1.el7.x86_64 #1 SMP Wed Mar 7 19:03:37 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
$ kubectl version
The text was updated successfully, but these errors were encountered: