This doesn't appear to be related to DNS, and the BZ of which this is a clone had component "Networking" and subcomponent "ovn-kubernetes", so I am setting the component and subcomponent on this BZ to match.
It looks like we need to backport https://github.com/ovn-org/ovn/commit/1bb32e0f8146d7f4fff84af5e3d2836ebe939e04 to ovn2.13-20.12 for OCP 4.7 and 4.8.
Once https://bugzilla.redhat.com/show_bug.cgi?id=2049011 lands, we can bump ovn-k and this should be fixed.
(In reply to Casey Callendrello from comment #5)
> Once https://bugzilla.redhat.com/show_bug.cgi?id=2049011 lands, we can bump
> ovn-k and this should be fixed.
It landed in ovn2.13 on Feb 1st; we can cross-tag and bump ovnk Dockerfile for 4.8 and 4.7 at any time.
ovn21.09 in 4.9 and ovn21.12 in 4.10 have had the fix since the beginning.
@dcbw it doesn't seem to be published yet, or do we need to mirror it in to CI?
Will it be fixed in 4.7 ? I see that target release has been changed to 4.9 ?
(In reply to Casey Callendrello from comment #8)
> @dcbw it doesn't seem to be published yet, or do we need to
> mirror it in to CI?
We need to tag it into OCP repos, wait 6 hours, and update the Dockerfile to use it.
Tested and verified in 4.9.0-0.nightly-2022-02-12-152152
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.9.22 security 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.