Loading...

XML

Word

Printable

Type: Bug
Resolution: Unresolved
Priority: Undefined
Fix Version/s: None
Affects Version/s: 4.16.z
Component/s: Networking / ovn-kubernetes
Labels:
- SDN:OVNK:CNILiveMigration

Activity Type:
Quality / Stability / Reliability
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Story Points:
3
Severity:
None
Regression:
None

Target Backport Versions:
None
Target Version:
None
Release Blocker:
Rejected
Sprint:
CORENET Sprint 273
sprint_count:
1

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

PX Impact Score:

Release Note Status:
None
Release Note Type:
None
Release Note Text:
None

Escape Reason:
None
Escape Impact:
None
Corrective Measures:
None
SDLC stage when should've been found:
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:

Assignee:: Peng Liu

Reporter:: Tafhim Ul Islam

Need Info From:: None

Contributors:: None

QA Contact:: Zhanqi Zhao

Doc Contact:: None

Votes:: 0 Vote for this issue

Watchers:: 6 Start watching this issue

Created:: 2025/07/11 1:06 AM

Updated:: 2025/07/15 2:16 AM