From 50d078b531efbbeaf90c88781be397ff4a91b041 Mon Sep 17 00:00:00 2001 From: Sam Crauwels Date: Mon, 13 Apr 2026 14:11:55 +0200 Subject: [PATCH] fix(molecule): give repos_default enough memory for dnf on rockylinux9 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The scenario was running with memory_mb: 512, which is fine for the first converge but OOM-kills dnf during the idempotence re-run on rockylinux9 with release 8. The second pass re-imports the elasticstack role's packages task, which invokes dnf fresh and briefly pushes past the 512 MiB cgroup limit; the kernel SIGKILLs the module, Ansible reports rc: 137 / "No start of json char found" after three retries and the job fails. A recent full-matrix run caught this after the prior attempt timed out at 30 minutes in the same combo — same root cause, different symptom depending on when the OOM-killer arrived. Every other molecule scenario in the collection uses 2048+; 1024 is enough for the repos path (which runs no services) and keeps the container footprint small. --- molecule/repos_default/molecule.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/molecule/repos_default/molecule.yml b/molecule/repos_default/molecule.yml index 40bc769..924d7b8 100644 --- a/molecule/repos_default/molecule.yml +++ b/molecule/repos_default/molecule.yml @@ -9,7 +9,10 @@ driver: platforms: - name: "repos-def-${MOLECULE_DISTRO:-debian12}-r${ELASTIC_RELEASE:-9}${MOLECULE_RUN_SUFFIX}" distro: "${MOLECULE_DISTRO:-debian12}" - memory_mb: 512 + # 1024 MiB so dnf on rockylinux9 does not get OOM-killed during the + # security-packages install in the idempotence run. Every other + # scenario uses 2048+, this one was the outlier at 512. + memory_mb: 1024 provisioner: name: ansible env: