Skip to content

fix(molecule): give repos_default enough memory for dnf on rockylinux9#133

Merged
Oddly merged 1 commit intomainfrom
fix/repos-default-oom
Apr 13, 2026
Merged

fix(molecule): give repos_default enough memory for dnf on rockylinux9#133
Oddly merged 1 commit intomainfrom
fix/repos-default-oom

Conversation

@Oddly
Copy link
Copy Markdown
Owner

@Oddly Oddly commented Apr 13, 2026

repos_default was running with memory_mb: 512, which is tight enough that dnf on rockylinux9 gets OOM-killed during the security-packages install. The first converge squeaks by but the idempotence re-run triggers the kernel OOM-killer; Ansible reports rc: 137 / "No start of json char found" after three retries and the job fails. An earlier run on the same combo timed out at 30 minutes in idempotence — same root cause, different symptom depending on when the OOM-killer arrived.

Every other molecule scenario uses 2048+; 1024 is enough for a path that runs no services and keeps the container footprint modest.

I will kick off a workflow_dispatch of Test Role repos on this branch once merged to confirm the rockylinux9 + release 8 combo passes end-to-end.

Summary by CodeRabbit

  • Chores
    • Updated testing infrastructure configuration to optimize test environment resource allocation and improve performance during automated testing runs.

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.
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 13, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: fe0ce90c-97b0-4e7a-9a98-ecec3e7bbcb7

📥 Commits

Reviewing files that changed from the base of the PR and between 0e190b2 and 50d078b.

📒 Files selected for processing (1)
  • molecule/repos_default/molecule.yml

📝 Walkthrough

Walkthrough

The molecule/repos_default/molecule.yml configuration file is updated to increase the memory allocation for the repos-def-* platform from 512 MB to 1024 MB, with inline comments added to document the adjustment for rockylinux9 idempotence runs.

Changes

Cohort / File(s) Summary
Molecule Configuration
molecule/repos_default/molecule.yml
Memory allocation for repos-def-* platform increased from 512 MB to 1024 MB with explanatory comments for rockylinux9 scenario.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title directly and specifically describes the main change: increasing memory allocation for the repos_default Molecule scenario to fix dnf OOM issues on rockylinux9.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/repos-default-oom

Comment @coderabbitai help to get the list of available commands and usage tips.

@Oddly Oddly merged commit 02bbd79 into main Apr 13, 2026
17 checks passed
@Oddly Oddly deleted the fix/repos-default-oom branch April 13, 2026 12:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant