-
Bug
-
Resolution: Done
-
Blocker
-
None
-
rhel-9.6
-
None
-
No
-
Important
-
rhel-sst-image-builder
-
None
-
False
-
-
None
-
None
-
None
-
None
-
None
What were you trying to do that didn't work?
bib will hit out-of-memory issue when building anaconda-iso with default progress bar, but it works well if I append `--log-level debug -v`
It looks like the tests starting to fail since this MR.
I checked this renovate MR will update osbuild and bib submodule to the latest (same as rhel-10.0 branch), and the tests only failed on rhel-9.6.
Test log: https://artifacts.osci.redhat.com/testing-farm/9776ce40-86d6-401e-aeb1-844a9508cf3f/
What is the impact of this issue to you?
Failed to build anaconda-iso with bib
Please provide the package NVR for which the bug is seen:
quay.io/redhat-user-workloads/rhel-bootc-tenant/bootc-image-builder-9-6/bootc-image-builder-9-6@sha256:e7f01d7ee93ecafed1084a075a96ebee79639421e38c162e3e6cb824d63e04b2
How reproducible is this bug?:
100%
Steps to reproduce
sudo podman run --rm -it --privileged --pull=newer --security-opt label=type:unconfined_t \ -v /var/lib/containers/storage:/var/lib/containers/storage \ -v $(pwd)/config.toml:/config.toml:ro \ -v $(pwd)/output:/output \ quay.io/redhat-user-workloads/rhel-bootc-tenant/bootc-image-builder-9-6/bootc-image-builder-9-6@sha256:e7f01d7ee93ecafed1084a075a96ebee79639421e38c162e3e6cb824d63e04b2 \ --type anaconda-iso \ --chown "$(id -u "$(whoami)"):$(id -g "$(whoami)")" \ --tls-verify=false \ registry.stage.redhat.io/rhel9/rhel-bootc:9.6
Expected results
build successfully
Actual results
get stuck at
[6 / 9] Pipeline anaconda-tree [------------------------------------------------------------------------------------------------------------------->_________________________________________________________] 66.67% [7 / 9] Stage org.osbuild.dracut [------------------------------------------------------------------------------------------------------------------------------------>______________________________________] 77.78% Message: Starting module org.osbuild.dracut
and it eats up all available memory and generated a file named oom in CWD.