[github-actions]

Automated changelog sync from backport PR #20269 and #20249

Generated by the sync-backport-changelog workflow and manually resynced by @shashank-elastic for #20249

[github-actions]

TL;DR

The OOM-testing pipeline failed during EPR instance deployment because the EPR VM did not have a Docker container named package-registry. This is an EPR infrastructure/deployment failure, not a problem in the changelog-only PR.

Remediation

• Restore or recreate the package-registry container on the EPR VM, then rerun the failed Buildkite step.
• If the container was intentionally renamed or removed, update the external deploy-epr.sh deployment logic to use the current registry container/service name.
• No source change is indicated in this PR: the only changed file is packages/security_detection_engine/changelog.yml.

Investigation details

Root Cause

The failed job reached the EPR cache-refresh step after successfully building and uploading the endpoint package, then attempted to restart Docker container package-registry. Docker returned No such container on all five retries, so the deployment command exited with status 1.

Evidence

• Build: https://buildkite.com/elastic/integrations/builds/46426
• Job/step: Deploy EPR instance in appex-qa-stateful-security-prebuilt-rules-ftr-oom-testing
• Key log excerpt: lines 119-139 of the captured job log show the restart attempt, five Error response from daemon: No such container: package-registry failures, and exhausted retries; line 144 reports exit status 1.
• PR diff: changelog: security_detection_engine 9.4.8 (backport sync from PR #20269) #20271 modifies only packages/security_detection_engine/changelog.yml.

Verification

• The endpoint package build and upload completed before the failure.
• The failed deployment step was not rerun because the missing container requires EPR infrastructure remediation.

Follow-up

After the EPR VM is repaired, rerun build 46426 (or the failed job) to confirm the OOM test can proceed.

---

What is this? | From workflow: PR Buildkite Detective

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

[shashank-elastic]

Add backport entry from #20249

[github-actions]

✅ Elastic Docs Style Checker (Vale)

No issues found on modified lines!

---

The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

[infra-vault-gh-plugin-prod]

💔 Build Failed

• Buildkite Build
• Commit: b293e8f

Failed CI Steps

• :elastic-cloud:📊 [security_detection_engine] Test for OOM issues against 9.6.0-SNAPSHOT ECH
• :elastic-cloud:📊 [security_detection_engine] Test for OOM issues against 9.5.0-SNAPSHOT ECH

History

• 💔 Build #46472 failed d793a59
• 💔 Build #46466 failed 393ed86
• 💔 Build #46426 failed 59c2ca4

cc @shashank-elastic