-
Bug
-
Resolution: Not a Bug
-
Major
-
None
-
4.9.z
-
None
-
3
-
Sprint 227, Sprint 228
-
2
-
Rejected
-
False
-
Description of problem:
During an upgrade of an OSD cluster from 4.9.45 to 4.9.47, a customer experienced a spike of DNS resolution failures. It appears the DNS Operator was degraded which resulted in a rapid restart of dns-default pods. This in turn caused customer workloads to fail on DNS lookups.
Version-Release number of selected component (if applicable):
4.9.47
How reproducible:
Intermittent
Steps to Reproduce:
1. Setup a temporary pod to constantly perform a DNS lookup on redhat.com 2. Upgrade an Openshift from 4.9.45 to 4.9.47 3. Observe any DNS failures in temporary pod
Actual results:
DNS lookups will result in "Name or service not known"
Expected results:
No DNS look ups fail during upgrade
Additional info:
Please see OHSS-15297
