Loading...

XML

Word

Printable

Type: Bug
Resolution: Not a Bug
Priority: Critical
Fix Version/s: None
Affects Version/s: 4.12.z
Component/s: Node / CRI-O
Labels:
- cri-o
- crio
- kubelet

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

Hide

None

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

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

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

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:

Nodes are frequently going in Notready state

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

    4.12.30

How reproducible:

    No steps to reproduct

Steps to Reproduce:

    1.
    2.
    3.

Actual results:

    Nodes are notready

Expected results:

Nodes should be in Ready state

Additional info:

    - Able to see pleg error in the kubelet logs
    - The logs are frequently showing GRPC error 
grpc: received message larger than max (16828879 vs. 16777216)"
    - Restarted crio and kubelet service still no luck
    - Deleted all the exited containers
    - Rebooting the node is only solution that works temporarily

Assignee:: Node Team Bot Account

Reporter:: Sonigra Saurab

Need Info From:: None

Contributors:: None

QA Contact:: Sunil Choudhary

Doc Contact:: None

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2024/05/14 1:55 PM

Updated:: 2025/10/08 12:49 PM

Resolved:: 2024/05/21 4:07 PM