Loading...

XML

Word

Printable

Type: Bug
Resolution: Won't Do
Priority: Critical
Fix Version/s: None
Affects Version/s: 4.14
Component/s: Node / CRI-O
Labels:
- crio
- node
- pod
- triaged

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

Hide

None

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

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

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:

    Pods stuck in Container Creating Error due to CRIO storage issue.
Error in pods yaml: starting container process caused: exec: \"cluster-kube-scheduler-operator\": executable file not found in $PATH"

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

How reproducible:

    We are not able to reproduce this issue but the customer is facing this issue regularly.

Steps to Reproduce:

    1.
    2.
    3.

Actual results:

Expected results:

Additional info:

    A bug was opened for 4.5 which seems to reappear again.
Bug link: https://bugzilla.redhat.com/show_bug.cgi?id=1942536
Another link: https://bugzilla.redhat.com/show_bug.cgi?id=1922154

Assignee:: Peter Hunt

Reporter:: Uttkarsh Deshmukh

Need Info From:: None

Contributors:: None

QA Contact:: Min Li

Doc Contact:: None

Votes:: 1 Vote for this issue

Watchers:: 4 Start watching this issue

Created:: 2025/04/16 6:24 AM

Updated:: 2025/09/12 11:46 PM

Resolved:: 2025/06/09 3:27 PM