Loading...

XML

Word

Printable

Type: Bug
Resolution: Not a Bug
Priority: Undefined
Fix Version/s: None
Affects Version/s: 4.12.z
Component/s: Networking / DNS
Labels:
- ne-triaged

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

Hide

None

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

Target Backport Versions:
None
Target Version:
None
Release Blocker:
Rejected
Sprint:
NE Sprint 258
sprint_count:
1

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

PX Review Complete:
PX Priority Data:
PX Impact Score:
PX Technical Impact:

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:

   One dns pod out of 7 is resolving svchostname with wrong IP address, whereas all other pods are resolving correctly.

Version-Release number of selected component (if applicable):

    Version- 4.12.37

Actual results:

    when we try to resolve service hostname via dns-pod running on worker2, we are getting wrong IP, which doesn't exist in cluster.

Expected results:

    We expect to get correct service IP of the application.

Additional info:

When pod running on worker2 tries nslookup svc hostname, we are getting wrong IP, whereas when we do nslookup from pod running on any other node, we are getting right IP of service.

Assignee:: Andrey Lebedev

Reporter:: Utkarsh Gupta

Need Info From:: Utkarsh Gupta

Contributors:: None

QA Contact:: Hongan Li

Doc Contact:: None

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Created:: 2024/04/15 6:14 PM

Updated:: 2025/09/12 10:50 PM

Resolved:: 2024/09/03 2:38 PM