Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Critical
Fix Version/s: None
Affects Version/s: 4.15.z
Component/s: OLM / Registry
Labels:
- catalog-content

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

Hide

None

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

Target Backport Versions:
None
Target Version:
None
Release Blocker:
Rejected
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:

    The redhat-operators catalogsource pod is using high CPU which is going above 1 core and sometimes closer to 2 cores. It appears that the issue happens when registry polling happens every 10 mins.

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

    4.15.25

How reproducible:

    not sure but 2 customers have reported this already

Steps to Reproduce:

    1.
    2.
    3.

Actual results:

    redhat-operators pod uses very high CPU

Expected results:

    The pod should use reasonable amount of CPU like earlier

Additional info:

duplicates

OCPBUGS-36421 redhat-operators pod experiencing unusually high CPU utilization

Closed

is caused by

OCPBUGS-52422 OPM no longer prunes metadata from non-channel heads

Assignee:: Catherine Chan-Tse

Reporter:: Alok Singh

Need Info From:: None

Contributors:: None

QA Contact:: Jia Fan

Doc Contact:: None

Votes:: 1 Vote for this issue

Watchers:: 5 Start watching this issue

Created:: 2024/08/26 4:29 PM

Updated:: 2025/09/13 11:45 AM

Resolved:: 2024/09/06 8:53 AM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates

Hide