Loading...

XML

Word

Printable

Type: Bug
Resolution: Won't Do
Priority: Normal
Fix Version/s: None
Affects Version/s: 4.13.z
Component/s: Networking / DNS
Labels:

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

Hide

None

Show
None
Story Points:
1
Severity:
Moderate
Regression:
No

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

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

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 an upgrade from 4.12.26 to 4.13.13, the critical alert KubeletDown fired for approximately 20 minutes. My best guess is that it fired while the DNS operator was upgrading.

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

4.12.26 upgrading to 4.13.13

How reproducible:

Unsure

Steps to Reproduce:

1. Start OCP upgrades
2. Determine if KubeletDown fires

Actual results:

Expected results:

No critical alerts fire during OCP control plane upgrades

Additional info:

Assignee:: Miciah Masters

Reporter:: Michael Shen (Inactive)

Need Info From:: None

Contributors:: None

QA Contact:: Melvin Joseph

Doc Contact:: None

Votes:: 0 Vote for this issue

Watchers:: 8 Start watching this issue

Created:: 2023/10/06 7:26 PM

Updated:: 2025/10/11 7:10 AM

Resolved:: 2024/01/19 4:54 PM