[main][Automation] Update versions

[github-actions]

These files are used for picking the starting (pre-upgrade) or ending (post-upgrade) agent versions in upgrade integration tests.

The content is based on responses from https://www.elastic.co/api/product_versions and https://snapshots.elastic.co

The current update is generated based on the following requirements:

.package-version

{
  "version": "9.6.0-SNAPSHOT",
  "build_id": "9.6.0-606eef5e",
  "manifest_url": "https://snapshots.elastic.co/9.6.0-606eef5e/manifest-9.6.0-SNAPSHOT.json",
  "summary_url": "https://snapshots.elastic.co/9.6.0-606eef5e/summary-9.6.0-SNAPSHOT.html",
  "core_version": "9.6.0",
  "stack_version": "9.6.0-SNAPSHOT",
  "stack_build_id": "9.6.0-606eef5e-SNAPSHOT"
}

testing/integration/testdata/.upgrade-test-agent-versions.yml

{
  "UpgradeToVersion": "9.6.0",
  "CurrentMajors": 1,
  "PreviousMajors": 2,
  "PreviousMinors": 2,
  "SnapshotBranches": [
    "9.5",
    "9.4",
    "8.19"
  ]
}

[infra-vault-gh-plugin-prod]

Pinging @elastic/elastic-agent (Team:Elastic-Agent)

[infra-vault-gh-plugin-prod]

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

[infra-vault-gh-plugin-prod]

💔 Build Failed

• Buildkite Build
• Commit: fb7cc40

Failed CI Steps

• linux:amd64:tier1:sudo:fleet
• linux:amd64:tier1:sudo:fleet

History

[github-actions]

TL;DR

The failed linux:amd64:tier1:sudo:fleet step is an ESS/observability environment provisioning failure, not a test or source-code failure. The retry requested cluster hosted-ess-ea-it-vsmfh, but oblt-cli could not find its cluster config after waiting, so no Fleet integration tests ran.

Remediation

• Retry the Buildkite step; if it reproduces, inspect the observability-test-environments PR/Slack workflow for hosted-ess-ea-it-vsmfh and determine why the requested cluster was not materialized.
• Validate the 9.6.0-606eef5e ESS snapshot images used by this generated version update are available to the ESS template.
• No code change is indicated by this failure; the PR changes only .package-version.

Investigation details

Root Cause

The job successfully downloaded the 9.6.0 artifacts and started oblt-cli 8.0.13. During the retry path, .buildkite/scripts/steps/integration_tests_oblt-cli.sh:39-43 called ess_up, which requests the ESS cluster. The request was accepted, but the cluster config was still absent when the provisioning wait ended. The subsequent teardown also could not find the cluster and reported that it would auto-expire.

The PR diff contains only .package-version, changing the target from 9.5.0 to 9.6.0; the failing command stopped before mage build:integrationTestBinaries or the Fleet tests.

Evidence

• Build: https://buildkite.com/elastic/elastic-agent/builds/42802
• Job/step: linux:amd64:tier1:sudo:fleet
• Key log excerpt: cluster config for cluster_name=hosted-ess-ea-it-vsmfh not found in all clusters (03:02:54Z)
• Cleanup excerpt: failed to destroy cluster hosted-ess-ea-it-vsmfh - ephemeral cluster will auto-expire

Verification

• Reviewed the failed job log, PR [main][Automation] Update versions #15461 diff, ESS provisioning wrappers, and recent PR comments. No integration-test assertion or agent runtime error was reached.
• No flaky-test issue was found for this failure.

---

What is this? | From workflow: PR Buildkite Detective

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