Bug 2032930

Summary: Catalog image bloat leads to scheduler issues
Product: OpenShift Container Platform Reporter: Fabian Deutsch <fdeutsch>
Component: OLMAssignee: Kevin Rizza <krizza>
OLM sub component: OLM QA Contact: Jian Zhang <jiazha>
Status: CLOSED NOTABUG Docs Contact:
Severity: high    
Priority: unspecified CC: davegord
Version: 4.9   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-12-17 14:29:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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: