In another customer case, I noticed this too which is the same as #690433:
net.bridge.bridge-nf-call-ip6tables = 0
net.bridge.bridge-nf-call-iptables = 0
net.bridge.bridge-nf-call-arptables = 0
net.bridge.bridge-nf-filter-vlan-tagged = 0
These depend on the bridge module being loaded and due to this bug they aren't loaded at all. There is a workaround in the other bug that involves an additional upstart job to set the network related sysctls but this isn't a good solution, just a temp workaround.
In another customer case, I noticed this too which is the same as #690433: bridge- nf-call- ip6tables = 0 bridge- nf-call- iptables = 0 bridge- nf-call- arptables = 0 bridge- nf-filter- vlan-tagged = 0
net.bridge.
net.bridge.
net.bridge.
net.bridge.
These depend on the bridge module being loaded and due to this bug they aren't loaded at all. There is a workaround in the other bug that involves an additional upstart job to set the network related sysctls but this isn't a good solution, just a temp workaround.