I am sorry let me clarify
I am working on a bug for a CMS regarding stale conntrack entries after logical switch port deletion. The question is whether the CMS itself should clear the conntrack entry or if ovn should clear the entry itself? Who is responsible for clearing conntrack entries when a CMS tells ovn to delete resources? For further reference see this upstream ovn-kubernetes PR https://github.com/ovn-org/ovn-kubernetes/pull/1074 Sorry for the first message Jacob On 3/27/20 1:55 PM, Jacob Tanenbaum wrote: > Hello All, > > I am working on a bug for a CMS regarding stale conntrack entries > after logical switch port deletion. The question is whether the CMS > itself should > clear the conntrack entry or should the CMS or if ovn should clear the > entry itself? > Who is responsible for clearing conntrack entries when a CMS tells ovn to > delete resources? > > For further reference see this upstream ovn-kubernetes > PR:https://github.com/ovn-org/ovn-kubernetes/pull/1074 > > All input is appreciated > Jacob > _______________________________________________ > dev mailing list > d...@openvswitch.org > https://mail.openvswitch.org/mailman/listinfo/ovs-dev _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev