fix(molecule): give repos_default enough memory for dnf on rockylinux9#133
Merged
fix(molecule): give repos_default enough memory for dnf on rockylinux9#133
Conversation
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.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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