[Release] Update test environments for 9.5.1

[elastic-vault-github-plugin-prod]

Update test environment versions to the correct Elastic Stack version.

Merge only after the release of 9.5.0.

[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 three x-pack/metricbeat integration jobs failed before tests started because Docker could not resolve docker.elastic.co/elasticsearch/elasticsearch:9.5.0. This PR updates the test environment defaults to 9.5.0, but that stack image is not available yet.

Remediation

• Wait until the 9.5.0 Elastic Stack Docker images are published, then retry the Buildkite build.
• If CI must pass before publication, keep the metricbeat test defaults on the latest published stack version instead of 9.5.0, then rerun cd x-pack/metricbeat && mage goIntegTest / mage goFIPSOnlyIntegTest / mage pythonIntegTest after the image tag is available.

Investigation details

Root Cause

This is a dependency/image availability failure, not a test assertion failure. The PR changes metricbeat/docker-compose.yml:18 and metricbeat/docker-compose.yml:22 to default the x-pack-inherited Elasticsearch service to 9.5.0. The x-pack compose file extends that service at x-pack/metricbeat/docker-compose.yml:24-27, and the Elasticsearch test image Dockerfile builds from the upstream tag at metricbeat/module/elasticsearch/_meta/Dockerfile:2:

FROM docker.elastic.co/elasticsearch/elasticsearch:${ELASTICSEARCH_VERSION}

With the PR default ELASTICSEARCH_VERSION:-9.5.0, Compose tries to resolve docker.elastic.co/elasticsearch/elasticsearch:9.5.0, which the registry reports as missing.

Evidence

• Build: https://buildkite.com/elastic/beats/builds/49088
• Jobs/steps:
  • 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, repeated in all three failed jobs:

>> Building docker images

failed to solve: docker.elastic.co/elasticsearch/elasticsearch:9.5.0: failed to resolve source metadata for docker.elastic.co/elasticsearch/elasticsearch:9.5.0: docker.elastic.co/elasticsearch/elasticsearch:9.5.0: not found

>> Building docker images again

failed to solve: docker.elastic.co/elasticsearch/elasticsearch:9.5.0: failed to resolve source metadata for docker.elastic.co/elasticsearch/elasticsearch:9.5.0: docker.elastic.co/elasticsearch/elasticsearch:9.5.0: not found

Error: running "docker compose -p metricbeat_9_5_0_81068c0a4a-snapshot build" failed with exit code 17

The same PR also updates testing/environments/latest.yml:6, testing/environments/latest.yml:22, and testing/environments/latest.yml:32 to 9.5.0, so other jobs using the latest released environment may hit the same dependency until the release images exist.

Verification

• Read the failed Buildkite logs and PR diff.
• Did not rerun Docker-based integration tests locally because this environment does not support Docker-in-Docker, and the failure occurs during remote image resolution before test execution.

Follow-up

Retry should be sufficient once 9.5.0 images are published; otherwise revert/hold these test environment defaults until publication.

---

What is this? | From workflow: PR Buildkite Detective

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