[updatecli] update elastic stack version for testing 9.6.0-7392fd3c-SNAPSHOT

[github-actions]

Bump elastic-stack to latest snapshot version

Update snapshot.yml

1 file(s) updated with "$1=9.6.0-7392fd3c-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!

[github-actions]

TL;DR

The failing Buildkite step is an infrastructure/package mirror failure during Docker image packaging, not a code/test regression from this PR. The immediate action is to rerun the failed build (or harden the Dockerfile install step against transient APK mirror failures).

Remediation

• Retry Buildkite build 16671 for PR #7771; this failure signature is transient network/package-index fetch instability.
• In parallel, consider making the Dockerfile package install more resilient (e.g., split apk update/apk add, ensure deterministic retry behavior under /bin/sh, and/or pin to a base image/repo where shadow availability is stable).

Investigation details

Root Cause

The failure occurs while building the release Docker image in the Package x86_64 job, at Dockerfile:26 in the stage-1 RUN block that executes:

apk update && apk add --no-cache shadow

Observed log behavior shows:

• initial index fetch succeeds (OK: 119173 distinct packages available), then
• subsequent index fetch times out (operation timed out), followed by
• shadow (no such package) due to stale/failed index state.

This is consistent with transient package repository/network failure during build, not with the PR’s code change (PR #7771 only updates dev-tools/integration/.env, 1 line changed).

Evidence

• Build: https://buildkite.com/elastic/fleet-server/builds/16671
• Failed job: Package x86_64
• Step command: .buildkite/scripts/release_test.sh
• Key log excerpt:

WARNING: fetching (apk.cgr.dev/redacted) operation timed out
ERROR: unable to select packages:
  shadow (no such package):
    required by: world[shadow]
...
ERROR: failed to build: failed to solve: process "/bin/sh -c for iter in {1..10}; do apk update && apk add --no-cache shadow ..." did not complete successfully: exit code: 1

• Failing instruction reference: Dockerfile:26 (RUN for iter in {1..10}; do ... apk add --no-cache shadow ... done)

Verification

• Not run locally (workflow is read-only detective analysis).

Follow-up

No flaky-test issue reference applies here because this is not a test assertion flake; it is a packaging infrastructure/mirror timeout during container build.

---

What is this? | From workflow: PR Buildkite Detective

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