This issue is currently impacting jobs needed for 1.24 (4.11) kube rebase.
https://github.com/openshift/cluster-ingress-operator/pull/793 had the wrong BZ number and was linked in error.
Verified this bug on 4.12.0-0.nightly-2022-08-12-053438 with yaml file from https://bugzilla.redhat.com/show_bug.cgi?id=2086887#c16 # oc logs curl-deploy-55f5d4c56d-qr7zd + nslookup -timeout=30 -retry=0 ingress-canary.openshift-ingress-canary.svc.cluster.local Server: 172.30.0.10 Address: 172.30.0.10#53 Name: ingress-canary.openshift-ingress-canary.svc.cluster.local Address: 172.30.225.25 real 0m0.049s user 0m0.001s sys 0m0.006s + sleep 100000
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.12.0 bug fix and 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. https://access.redhat.com/errata/RHSA-2022:7399