Cause: Address set naming convention used in OVN-Kubernetes changed from 4.5 to 4.6 but migration to the new naming convention of existing address sets through an upgrade was not handled. Consequence: Network policies created in 4.5 with namespace selector criteria for their ingress or egress sections might not work correctly in 4.6 or later releases due to the fact that rely on matching old address sets that were not being kept updated with the pod IPs within such namespaces. These policies might allow or drop unexpected traffic. Workaround is to remove and recreate these policies. Fix: On OVN-Kubernetes upgrade to fixed version, address sets with old naming convention are removed and policy ACLs referencing this old address sets are updated referencing the address sets following the new naming convention. Result: Affected network policies created in 4.5 should start working correctly again after upgrade.