-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.16.z
-
Quality / Stability / Reliability
-
False
-
-
3
-
None
-
None
-
None
-
None
-
Rejected
-
CORENET Sprint 273
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
During one of the incidents, we noticed that DNS was failing. We observed that customer pods were blocked from launching. SRE rolled all the openshift-dns pods to let customer workloads launch.
Version-Release number of selected component (if applicable):
4.16.41
How reproducible:
We came across the issue during an incident. We still do not have a clear idea how to reproduce this reliably.
Steps to Reproduce:
We came across the issue during an incident. We still do not have a clear idea how to reproduce this reliably.
Actual results:
Some Machine API Controller pods were showing this error with DNS
Post \"https://sts.amazonaws.com/\": dial tcp: lookup sts.amazonaws.com on 10.*.*.*:*: read udp 10.*.*.*:*->10.*.*.*:*: i/o timeout
Expected results:
DNS resolution should be generally stable during migration
Additional info: