Bug 2032930 - Catalog image bloat leads to scheduler issues
Summary: Catalog image bloat leads to scheduler issues
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: OLM
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Kevin Rizza
QA Contact: Jian Zhang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-15 14:00 UTC by Fabian Deutsch
Modified: 2021-12-17 14:29 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-12-17 14:29:20 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Fabian Deutsch 2021-12-15 14:00:08 UTC 
Description of problem:
In bug #1984442 we noticed that there are very many OLM catalog images.
The problem is that the OCP scheduler has a default limit of taking at max 50 images per node into account when doing scheduling.
Because of these catalog images, some nodes have more than 50 images, and therefore some workloads will not be scheduled anymore if this condition occurs.

While there are manual pruning mechanisms, it would be important tha OLM by itself could avoid creating so much bloat.

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


How reproducible:


Steps to Reproduce:
1. Not totally clear, likely long running large clusters.
2.
3.

Actual results:
Bug 1984442 is caused

Expected results:
OLM is not a cause for 1984442

Additional info:
Note You need to log in before you can comment on or make changes to this bug.