[Release] Update test environments for 9.4.2

[elastic-vault-github-plugin-prod]

Update test environment versions to the correct Elastic Stack version.

Merge only after the release of 9.4.1.

[github-actions]

🤖 GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)
• /test : Run the Buildkite pipeline.

[github-actions]

TL;DR

All 3 failing Buildkite jobs are failing before tests run because Docker image resolution fails for docker.elastic.co/elasticsearch/elasticsearch:9.4.1 (not found).
The PR updates test env image tags to 9.4.1, but that tag is not available in CI right now, so docker compose ... build exits with status 17.

Remediation

• Update the version pins in this PR to a currently published tag (or wait to merge until 9.4.1 images are published and rerun CI).
• Re-run x-pack/metricbeat integration jobs after adjusting the version pins.

Investigation details

Root Cause

The same Docker image resolution error appears in all 3 failed jobs (goIntegTest, goFIPSOnlyIntegTest, pythonIntegTest), so this is not a test assertion failure; it is an environment/image-tag failure during image build.

The PR diff changes multiple test environment tags to 9.4.1, including:

• metricbeat/docker-compose.yml:18,22,39,43,54,58
• x-pack/metricbeat/docker-compose.yml:33,37
• testing/environments/latest.yml:6,22,32

Evidence

• Build: https://buildkite.com/elastic/beats/builds/45638
• Failing jobs:
  • x-pack/metricbeat: Go Integration Tests (Module)
  • x-pack/metricbeat: Go fips140=only Integration Tests (Module)
  • x-pack/metricbeat: Python Integration Tests (Module)
• Key log excerpt (present in all 3 logs):

failed to solve: docker.elastic.co/elasticsearch/elasticsearch:9.4.1: failed to resolve source metadata for docker.elastic.co/elasticsearch/elasticsearch:9.4.1: docker.elastic.co/elasticsearch/elasticsearch:9.4.1: not found
Error: running "docker compose -p metricbeat_9_4_1_ab9a4da0e9-snapshot build" failed with exit code 17

Verification

• Not run locally; diagnosis is based on direct Buildkite failure logs and PR diff.

Follow-up

If 9.4.1 publication timing is the blocker, rerun this PR after the image is available (or pin to the currently available release tag in the meantime).

---

What is this? | From workflow: PR Buildkite Detective

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