-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
None
-
Quality / Stability / Reliability
-
False
-
-
False
-
None
-
None
-
None
-
None
-
None
When I debug issues for the test operator-e2e-hypershift-local-graph-data, it is noticed that it generated a log file of 700M.
$ oc --kubeconfig /tmp/k.c logs -n openshift-update-service example-6975d5c895-zgrbc -c graph-builder -f 2>&1 | tee -a ~/Downloads/example-6975d5c895-zgrbc.pod.log $ ll example-6975d5c895-zgrbc.pod.log -rw-r--r--@ 1 hongkliu staff 706M Apr 23 15:32 example-6975d5c895-zgrbc.pod.log
A run of the e2e test could scape over 9k releases.
[2025-04-23T15:38:31Z INFO graph_builder::graph] graph update completed, 9311 valid releases
To avoid slowing further down QUAY.IO which has been known slower than before, graph-builder might do things as needed.
AC:
graph-builder can control the amount of releases to scape and scape as few releases as possible in e2e test.