-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
4.21
-
None
-
None
-
False
-
-
None
-
Critical
-
None
-
None
-
None
-
Proposed
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Install a custom DNS cluster, installation process succeeded, but checking the coredns pod, it reported following errors continuously,
[ERROR] plugin/errors: 2 . NS: read udp 10.0.0.4:58260->168.63.129.16:53: i/o timeout
[ERROR] plugin/errors: 2 . NS: read udp 10.0.0.4:51842->10.0.0.4:53: i/o timeout
[ERROR] plugin/errors: 2 cdn01.quay.io. A: read udp 10.0.0.4:52134->168.63.129.16:53: i/o timeout
[ERROR] plugin/errors: 2 . NS: read udp 10.0.0.4:46658->10.0.0.4:53: i/o timeout
[ERROR] plugin/errors: 2 cdn01.quay.io. A: read udp 10.0.0.4:54452->168.63.129.16:53: i/o timeout
[ERROR] plugin/errors: 2 . NS: read udp 10.0.0.4:43536->168.63.129.16:53: i/o timeout
the above error came from https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_release/71412/rehearse-71412-periodic-ci-openshift-release-master-ci-4.21-e2e-azure-custom-dns-techpreview/1993667161335271424
Version-Release number of selected component (if applicable):
4.21.0-0.ci-2025-11-26-030640
How reproducible:
Always
Steps to Reproduce:
1. install a custom DNS cluster on AWS or Azure.
2.
3.
Actual results:
Install succeeded, but coredns reported above error continuously.
Expected results:
Install succeeded, no errors in coredns pod log.
Additional info:
no such errors on GCP platform.