Fix CI: container memory, verify retries, diagnostics restart#80
Merged
Conversation
The 1024 MB limit was too tight — dnf/yum with rpm scriptlets spikes memory during package install, causing OOM kills (rc=137) on Rocky 9.
Add retries to _cat/nodes checks in no-security, upgrade, and elasticstack_default verify playbooks. ES can return HTTP 500 (array_index_out_of_bounds_exception) briefly after startup when node info isn't fully initialized. Fix diagnostics scenario restart failure on debian13 r9 by clearing systemd failure state and waiting for node lock release before restarting ES after the intentional bad-config crash test.
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
1 participant
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.
Standalone logstash and beats containers had 1024 MB memory limits which caused OOM kills (rc=137) during package installation on Rocky 9. Bumped to 2048 MB.
The
_cat/nodesAPI can return HTTP 500 (array_index_out_of_bounds_exception) briefly after ES startup when node info isn't fully initialized. Added retries to the node check in the no-security, upgrade, and elasticstack_default verify playbooks.The diagnostics scenario consistently failed on debian13 r9 because ES couldn't restart after the intentional bad-config crash test. systemd's failure state and ES node locks weren't cleared before the recovery restart. Added
systemctl reset-failedand a 5-second pause.