Bug 1956980 - OVN-Kubernetes leaves stale AddressSets around if the deletion was missed.
Summary: OVN-Kubernetes leaves stale AddressSets around if the deletion was missed.
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.7
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.7.z
Assignee: Casey Callendrello
QA Contact: Anurag saxena
Depends On: 1947176
TreeView+ depends on / blocked
Reported: 2021-05-04 19:30 UTC by Casey Callendrello
Modified: 2021-06-15 09:27 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-06-15 09:27:08 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift ovn-kubernetes pull 523 0 None open Bug 1956980: [release-4.7] fix ForEachAddressSet() as it is not calling the callback functions 2021-05-04 19:31:27 UTC
Red Hat Product Errata RHSA-2021:2286 0 None None None 2021-06-15 09:27:55 UTC

Description Casey Callendrello 2021-05-04 19:30:28 UTC
This bug was initially created as a copy of Bug #1947176

I am copying this bug because: 

Upstream PR https://github.com/ovn-org/ovn-kubernetes/pull/2152 fixes a bug where ForEachAddressSet didn't work.

This means that we won't delete old address sets if the deletion is missed, say, because ovn-k was restarting.

If another namespace or NetworkPolicy comes into existence with the same name, it will have spurious IPs in the address set.

We should backport this fix as appropriate.

Comment 4 Siddharth Sharma 2021-06-04 18:39:14 UTC
This bug will be shipped as part of next z-stream release 4.7.15 on June 14th, as 4.7.14 was dropped due to a regression https://bugzilla.redhat.com/show_bug.cgi?id=1967614

Comment 8 errata-xmlrpc 2021-06-15 09:27:08 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.7.16 security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.