[github-actions]

Bump elastic-stack to latest snapshot version

Update snapshot.yml

1 file(s) updated with "$1=9.6.0-774b1868-SNAPSHOT": * dev-tools/integration/.env

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!

[Copilot]

🟢 Approval recommended

The isolated snapshot-pin update has no identified defects; image availability and integration execution remain unverified.

No open issues 🎉

What changed in this PR

Updates Fleet Server’s integration-test environment to use the latest pinned Elasticsearch snapshot.

Changes:

• Bumps ELASTICSEARCH_VERSION from 9.6.0-c3504f11-SNAPSHOT to 9.6.0-774b1868-SNAPSHOT.

File	Description
dev-tools/​integration/​.env	Updates the Elasticsearch snapshot pin for integration testing.

_{Review effort: Balanced}

[github-actions]

TL;DR

Both failing Buildkite jobs (Cloud e2e Test and Cloud e2e FIPS Test) exited with status 1, but the captured logs only show teardown (mage test:cloudE2EDown) after a prior failure. The actual failing command/error is missing, so this run is not attributable to a code change with current evidence.

Remediation

• Re-run build #17777 with full step logs (or artifact upload) for .buildkite/scripts/cloud_e2e_test.sh before cleanup output.
• Add explicit failure echo around each command in cloud_e2e_test.sh (especially mage test:cloudE2EUp and mage test:cloudE2ERun) so the first failing command is preserved in tail logs.
• After getting full logs, classify as code/test/infra and apply targeted fix.

Investigation details

Root Cause

Current failure evidence is incomplete. Both log files start mid-teardown and end with generic non-zero exit.

• /tmp/gh-aw/buildkite-logs/fleet-server-gcloud-cloud-e2e-test.txt:136-138
• /tmp/gh-aw/buildkite-logs/fleet-server-gcloud-cloud-e2e-fips-test.txt:136-138

The PR itself changes one file (dev-tools/integration/.env, +1/-1 in commit b0820a09), but no log evidence ties the failure to that diff.

Evidence

• Build: https://buildkite.com/elastic/fleet-server/builds/17777
• Jobs/steps:
  • :gcloud: Cloud e2e Test
  • :gcloud: Cloud e2e FIPS Test
• Key log excerpt (both jobs):
  • Destroy complete! Resources: 1 destroyed.
  • 🚨 Error: The command exited with status 1
  • user command error: exit status 1

Verification

• Queried PR metadata/comments for [updatecli] update elastic stack version for testing 9.6.0-774b1868-SNAPSHOT #8128.
• Read both failing step logs listed in /tmp/gh-aw/buildkite-failures.txt.
• Checked for an existing flaky-test issue match related to Cloud e2e in elastic/fleet-server; no direct match found.
• No local repro run performed (cloud credentials/environment unavailable in this sandbox).

Follow-up

If full logs show cloud deployment did not become ready, cloud e2e tests cannot be executed, treat as infrastructure/transient cloud readiness and retry; if they show test assertions in mage test:cloudE2ERun, treat as test/code and patch accordingly.

---

What is this? | From workflow: Observability Agentic Workflow — Status

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

[elastic-vault-github-plugin-prod]

Dependency Update Analysis

Summary: This PR bumps the Elasticsearch snapshot image tag used by integration/cloud test tooling (9.6.0-c3504f11-SNAPSHOT → 9.6.0-774b1868-SNAPSHOT); overall risk is low-to-moderate due to snapshot churn, with no repo-facing breaking usage identified.

ELASTICSEARCH_VERSION (9.6.0-c3504f11-SNAPSHOT → 9.6.0-774b1868-SNAPSHOT)

Ecosystem: CI / container / snapshot image pin

Check	Result
Breaking changes	✅ None found in repository usage (tag value consumed as image/version input only)
Testable in PR	✅ Yes — PR Buildkite pipeline runs integration tests on commit

Changelog highlights (old → new)

• This is a snapshot build-id rotation within the same 9.6.0 line.
• Upstream human-readable release notes/changelog for snapshot build IDs were not available from repository-local metadata; analysis is based on the local diff and usage.
• No CVE/GHSA entries are derivable from the local metadata for this snapshot bump.

Usage in this repository

• dev-tools/integration/.env:3 defines ELASTICSEARCH_VERSION (the updated pin).
• dev-tools/integration/docker-compose.yml:6,48,91 uses it for Elasticsearch container images.
• magefile.go:1158 uses it as DOCKER_BASE_IMAGE_TAG fallback for custom agent image flow.
• magefile.go:2437-2449 reads it for cloud E2E stack image tag derivation.
• PR validation path exists: .buildkite/pull-requests.json (build_on_commit: true for pipeline fleet-server) and .buildkite/pipeline.yml:196-204 runs .buildkite/scripts/integration_test.sh, which executes mage test:integration.

Compatibility assessment

• No API/input contract changes in this repo: only an env tag value changed.
• Scope is CI/dev/test infrastructure (integration + related tooling), not production runtime dependency wiring.
• Snapshot builds can include behavioral changes between hashes, but PR CI exercises the affected test path and the bump remains within the same 9.6.0 stream.

Labels Applied

• oblt-aw/ai/merge-ready — applied (low-to-moderate risk, no repo-facing breaking usage found, CI/dev-only impact with PR test coverage path).

---

What is this? | From workflow: Observability Agentic Workflow — Pull Request

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

[github-actions]

Automerge skipped

Automerge skipped this pull request because the changed files do not match any configured dependency collection.

If this update should be automerged, ask a maintainer to add or adjust a collection, or merge the pull request manually.

See Opt in or opt out for how to enable or disable Automerge collections on the Control Plane Dashboard.

Collections currently enabled for automerge: github-actions, pre-commit, vm-images

Changed files considered:

• dev-tools/integration/.env

[Copilot]

Note

Copilot could not run the full agentic suite for this review because it was automatically requested on a bot-authored pull request. Request a review from Copilot under Reviewers to retry with the full agentic suite. Improved support for bot-authored pull requests is coming soon.

Copilot review overview

No open issues 🎉

_{Review effort: Lite}