On 5/17/22 16:10, Dumitru Ceara wrote: > Hi Justin, > > I know it's a while ago since this patch [0][1] made it in OVN but I was > wondering if you remembered some of the reasons behind doing this. > > More recently, OVN got a new feature to allow the CMS to explicitly > specify a zone ID to be used for conntrack for gateway routers [2]. > > The reason behind that was that, in some cases, ovn-kubernetes shares > the gateway router conntrack zone with the host [3]. > > The fact that an ovn-controller restart flushes the shared zone becomes > an issue sometimes. We're trying to see if there's a way to avoid that, > potentially via an ovn-controller cmdline argument or configuration. > > But before that, I wonder if you know of any CMS that relies on the > flush-on-use behavior.
Sorry for the noise. I think we figured out the context and we also found the bug that was strictly related to conntrack zone ID 0. I posted a fix for that: https://patchwork.ozlabs.org/project/ovn/patch/[email protected]/ Regards, Dumitru _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
