[Release] Update test environments for 9.3.9

[elastic-vault-github-plugin-prod]

Update test environment versions to the correct Elastic Stack version.

Merge only after the release of 9.3.8.

[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 failed x-pack/metricbeat integration jobs stop during Docker image resolution, before any tests run. The PR switches the test environment to Elasticsearch 9.3.8, but the Buildkite runner reports that docker.elastic.co/elasticsearch/elasticsearch:9.3.8 does not exist yet.

Remediation

• Merge or rerun this PR only after the 9.3.8 Elasticsearch image (and the corresponding 9.3.8 test images) has been published, or temporarily keep the test environment on 9.3.7 until release publication completes.
• Re-run goIntegTest, goFIPSOnlyIntegTest, and pythonIntegTest after the images are available.

Investigation details

Root Cause

This is a release-order/configuration failure, not a Go, FIPS, or Python test failure. The PR changes testing/environments/latest.yml from 9.3.7 to 9.3.8 and the metricbeat compose defaults to 9.3.8. The x-pack/metricbeat compose build consequently attempts to resolve the 9.3.8 Elasticsearch base image and fails before test execution.

Evidence

• Build: https://buildkite.com/elastic/beats/builds/49923
• Jobs: beats-xpack-metricbeat build 34495 (goIntegTest, goFIPSOnlyIntegTest, pythonIntegTest)
• Key log excerpt: failed to solve: docker.elastic.co/elasticsearch/elasticsearch:9.3.8: failed to resolve source metadata ...: not found
• Each job exits while running docker compose -p metricbeat_9_3_8_146378a568-snapshot build, with exit status 17.

Verification

The three provided job logs show the same image-resolution error and no test artifacts were produced. No local integration test was run because the required 9.3.8 image is unavailable.

Follow-up

The PR description already states it should merge only after 9.3.8 is released; once publication is complete, retrying the Buildkite build should validate the change.

---

What is this? | From workflow: PR Buildkite Detective

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