[updatecli] update elastic stack version for testing 8.19.14-2b5d6aff

[github-actions]

Bump elastic-stack to latest snapshot version

Update snapshot.yml

1 file(s) updated with "$1:8.19.14-2b5d6aff-SNAPSHOT": * testing/environments/snapshot.yml

GitHub Action workflow link

---

Created automatically by Updatecli Options: Most of Updatecli configuration is done via its manifest(s). If you close this pull request, Updatecli will automatically reopen it, the next time it runs. If you close this pull request and delete the base branch, Updatecli will automatically recreate it, erasing all previous commits made. Feel free to report any issues at github.com/updatecli/updatecli. If you find this tool useful, do not hesitate to star our GitHub repository as a sign of appreciation, and/or to tell us directly on our chat!

[github-actions]

TL;DR

Buildkite failed before any project build/test steps ran: multiple jobs could not clone/fetch elastic/beats due repeated GitHub HTTP 500 responses (exit status 128). Immediate action is to retry the Buildkite build; this appears to be transient infrastructure/network/backend failure, not a PR code defect.

Remediation

• Retry Buildkite build https://buildkite.com/elastic/beats/builds/43307 (and downstream failed pipelines) once GitHub service is healthy.
• If retries still fail, inspect checkout/auth transport config in Buildkite hooks (HTTPS token checkout path) and capture request IDs/timestamps for GitHub support.

Investigation details

Root Cause

All 4 failures occur during repository checkout/pipeline-upload bootstrap, not compilation or tests.

Observed failure pattern in logs:

• remote: Internal Server Error
• fatal: unable to access 'https://github.com/elastic/beats.git/': The requested URL returned error: 500
• or error: RPC failed; HTTP 500 curl 22 ... then fatal: expected flush after ref listing
• repeated across retry attempts, ending with 🚨 Error: cloning git repository: exit status 128

This indicates infrastructure/external service failure during git fetch/clone. The PR commit was not reliably checked out in those failed jobs, so no source-level regression evidence is present.

Evidence

• Build: https://buildkite.com/elastic/beats/builds/43307
• Failed jobs:
  • Upload Pipeline: .buildkite/heartbeat/heartbeat-pipeline.yml
  • Upload Pipeline: .buildkite/x-pack/pipeline.xpack.osquerybeat.yml
  • Upload Pipeline: .buildkite/libbeat/pipeline.libbeat.yml
  • Upload Pipeline: .buildkite/x-pack/pipeline.xpack.libbeat.yml
• Key log excerpts from /tmp/gh-aw/buildkite-logs/*:
  • remote: Internal Server Error
  • fatal: unable to access 'https://github.com/elastic/beats.git/': The requested URL returned error: 500
  • ⚠️ Warning: Checkout failed! ... (Attempt 1/3 ... Attempt 3/3)

Verification

• No repo tests were run: jobs failed before checkout/bootstrap completed.

Follow-up

• If this reproduces after retry, correlate with GitHub status/incident windows and collect Buildkite agent checkout hook logs for transport/auth diagnostics.

Note

🔒 Integrity filtering filtered 1 item

Integrity filtering activated and filtered the following item during workflow execution.
This happens when a tool call accesses a resource that does not meet the required integrity or secrecy level of the workflow.

• pr:[updatecli] update elastic stack version for testing 8.19.14-2b5d6aff #49818 (pull_request_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)

---

What is this? | From workflow: PR Buildkite Detective

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

[mergify]

Automatically approving mergify

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-04-01 08:39 UTC · Rule: default
• ✅ Checks started · on draft merge queue: embarking 8.19 (ef695b8) and #49818 together #49835
• 🚫 Left the queue — 2026-04-01 09:07 UTC · at 57b31b5e29f190aa0d06b8d73e12ca7f6792ef41

This pull request spent 27 minutes 45 seconds in the queue, including 35 seconds running CI.

Required conditions to merge

• check-success=CLA
• check-success=buildkite/beats
• any of [🛡 GitHub branch protection]:
  • check-neutral = CLA
  • check-skipped = CLA
  • check-success = CLA
• any of [🛡 GitHub branch protection]:
  • check-neutral = buildkite/beats
  • check-skipped = buildkite/beats
  • check-success = buildkite/beats
• any of [🛡 GitHub branch protection]:
  • check-neutral = buildkite/docs-build-pr
  • check-skipped = buildkite/docs-build-pr
  • check-success = buildkite/docs-build-pr
• #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule [org] Require a PR for Renovate]
  • [updatecli] update elastic stack version for testing 8.19.14-2b5d6aff #49818
• #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule [org] Require a PR]
  • [updatecli] update elastic stack version for testing 8.19.14-2b5d6aff #49818
• #changes-requested-reviews-by = 0 [🛡 GitHub repository ruleset rule [org] Require a PR for Renovate]
  • [updatecli] update elastic stack version for testing 8.19.14-2b5d6aff #49818
• #changes-requested-reviews-by = 0 [🛡 GitHub repository ruleset rule [org] Require a PR]
  • [updatecli] update elastic stack version for testing 8.19.14-2b5d6aff #49818

Reason

New commits have been added to the draft pull request that were not made by Mergify

Hint

If you want to requeue this pull request, you can post a @mergifyio queue comment.