Loading...

XML

Word

Printable

Type: Bug
Resolution: Won't Do
Priority: Normal
Fix Version/s: None
Affects Version/s: 4.13.z, 4.12.z
Component/s: oc
Labels:
- telco-4.12.z
- telco-priority-2

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

Hide

None

Show
None
Story Points:
None
Severity:
Important
Regression:
None
Latest Status Summary:
8/23: telco priority bumped up to 2/important for 4.12.z; KNIECO-6751

Target Backport Versions:
None
Target Version:
None
Release Blocker:
Rejected
Sprint:
None

Internal Whiteboard:
RH Private Keywords:

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

PX Review Complete:
PX Priority Data:
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:

Wrong status for evicted pod

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

4.12.z

How reproducible:

100% on 4.12/4.13

Steps to Reproduce:

1. Create a simple deployment with a pod running.
2. Set limits on the project for CPU/memory less than what the pod is using.
3. The pod will get evicted and show status as ContainerStatusUnknown, Completed, Error etc.

Actual results:

The pod shows status as ContainerStatusUnknown, Completed, Error etc. on eviction.

Expected results:

The pod should show status as Evicted

Additional info:

The issue seems same as https://github.com/kubernetes/kubernetes/issues/105467. This issue is not getting traction it seems.

clones

OCPBUGS-5750 Wrong status for evicted pod

Closed

Assignee:: Arda Guclu

Reporter:: Alok Singh

Need Info From:: None

Contributors:: None

QA Contact:: Ying Zhou

Doc Contact:: None

Votes:: 0 Vote for this issue

Watchers:: 9 Start watching this issue

Created:: 2023/08/17 1:59 PM

Updated:: 2025/09/13 2:51 AM

Resolved:: 2024/01/29 7:09 PM