[main][Automation] Bump VM Image version to 1782878510

[github-actions]

Bump vm-images to latest version

Update all Buildkite pipeline files (Azure)

14 file(s) updated with "$1: \"1.0.1782878510\"": * .buildkite/x-pack/pipeline.xpack.osquerybeat.yml * .buildkite/x-pack/pipeline.xpack.packetbeat.yml * .buildkite/auditbeat/auditbeat-pipeline.yml * .buildkite/filebeat/filebeat-pipeline.yml * .buildkite/heartbeat/heartbeat-pipeline.yml * .buildkite/winlogbeat/pipeline.winlogbeat.yml * .buildkite/x-pack/pipeline.xpack.auditbeat.yml * .buildkite/x-pack/pipeline.xpack.filebeat.yml * .buildkite/x-pack/pipeline.xpack.metricbeat.yml * .buildkite/x-pack/pipeline.xpack.winlogbeat.yml * .buildkite/libbeat/pipeline.libbeat.yml * .buildkite/metricbeat/pipeline.yml * .buildkite/packetbeat/pipeline.packetbeat.yml * .buildkite/x-pack/pipeline.xpack.heartbeat.yml

Update all Buildkite pipeline files (AWS/GCP)

21 file(s) updated with "$1: \"platform-ingest-beats-$2-1782878510\"": * .buildkite/x-pack/pipeline.xpack.winlogbeat.yml * .buildkite/packaging.pipeline.yml * .buildkite/auditbeat/auditbeat-pipeline.yml * .buildkite/ironbank-validation.yml * .buildkite/x-pack/pipeline.xpack.auditbeat.yml * .buildkite/x-pack/pipeline.xpack.libbeat.yml * .buildkite/x-pack/pipeline.xpack.metricbeat.yml * .buildkite/x-pack/pipeline.xpack.otel.yml * .buildkite/x-pack/pipeline.xpack.packetbeat.yml * .buildkite/aws-tests-pipeline.yml * .buildkite/libbeat/pipeline.libbeat.yml * .buildkite/metricbeat/pipeline.yml * .buildkite/x-pack/pipeline.xpack.dockerlogbeat.yml * .buildkite/x-pack/pipeline.xpack.filebeat.yml * .buildkite/x-pack/pipeline.xpack.heartbeat.yml * .buildkite/filebeat/filebeat-pipeline.yml * .buildkite/packetbeat/pipeline.packetbeat.yml * .buildkite/x-pack/pipeline.xpack.osquerybeat.yml * .buildkite/heartbeat/heartbeat-pipeline.yml * .buildkite/winlogbeat/pipeline.winlogbeat.yml * .buildkite/deploy/kubernetes/deploy-k8s-pipeline.yml

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!

[botelastic]

This pull request doesn't have a Team:<team> label.

[github-actions]

TL;DR

Heartbeat’s two FIPS unit-test jobs passed their Go/Python tests, then failed during teardown because the Buildkite test-collector plugin could not find BUILDKITE_ANALYTICS_TOKEN. The Metricbeat failure is the same module.NewWrapper compile error already reported in the previous detective comment, so I am not duplicating that remediation here.

Remediation

• Add the heartbeat pipeline slug to the analytics-token setup in .buildkite/hooks/pre-command:13-25, or otherwise ensure BUILDKITE_ANALYTICS_TOKEN is exported before Heartbeat steps that use test-collector#v1.10.2 run.
• Rerun the failed Heartbeat FIPS steps; no Heartbeat test failure needs code-level debugging based on these logs.
• For Metricbeat, apply the existing remediation from the prior detective comment: pass &beat.Info{Logger: logptest.NewTestingLogger(t, "")} to module.NewWrapper at metricbeat/mb/module/runner_test.go:173.

Investigation details

Root Cause

The Heartbeat FIPS steps use test-collector#v1.10.2 in .buildkite/heartbeat/heartbeat-pipeline.yml:122-127 and .buildkite/heartbeat/heartbeat-pipeline.yml:149-154. The shared hook that prepares BUILDKITE_ANALYTICS_TOKEN only runs for selected pipeline slugs in .buildkite/hooks/pre-command:13-25; that allowlist includes beats-xpack-heartbeat but not heartbeat.

Both Heartbeat logs show tests completed successfully before the teardown failure, so this is a Buildkite configuration/infrastructure failure rather than a Heartbeat code/test failure.

The Metricbeat job still has a real compile-time failure: metricbeat/mb/module/runner_test.go:173 passes logptest.NewTestingLogger(t, ""), but module.NewWrapper is declared with info *beat.Info as its third argument in metricbeat/mb/module/wrapper.go:93. That root cause and fix were already posted in the existing detective comment on this PR.

Evidence

• Build: https://buildkite.com/elastic/beats/builds/48835
• Heartbeat job/step: :ubuntu: Heartbeat: Ubuntu x86_64 Unit Tests with requirefips build tag
• Heartbeat log excerpt:

>> go test: Unit Test Passed
========================================================== 25 passed, 3 skipped, 2 warnings in 26.45s ==========================================================
Missing BUILDKITE_ANALYTICS_TOKEN environment variable
🚨 Error: Error tearing down job executor: running "plugin test-collector-buildkite-plugin pre-exit" shell hook: The plugin test-collector-buildkite-plugin pre-exit hook exited with status 1

• Heartbeat job/step: :ubuntu: Heartbeat: Ubuntu x86_64 fips140=only Unit Tests
• Heartbeat log excerpt:

>> go test: Unit-FIPS-only Test Passed
Missing BUILDKITE_ANALYTICS_TOKEN environment variable
🚨 Error: Error tearing down job executor: running "plugin test-collector-buildkite-plugin pre-exit" shell hook: The plugin test-collector-buildkite-plugin pre-exit hook exited with status 1

• Metricbeat job/step: Metricbeat: Run check/update
• Metricbeat log excerpt:

vet: mb/module/runner_test.go:173:51: cannot use logptest.NewTestingLogger(t, "") (value of type *logp.Logger) as *beat.Info value in argument to module.NewWrapper
Error: failed running go vet, please fix the issues reported: running "go vet ./..." failed with exit code 1

Verification

• Reproduced the Metricbeat compile error with cd metricbeat && go test ./mb/module -run TestRunnerStop_ClientClosedAfterPublishGoroutine -count=1.
• Did not rerun the Heartbeat Buildkite teardown locally because the failure depends on Buildkite plugin execution and CI-provided analytics-token setup.

---

What is this? | From workflow: PR Buildkite Detective

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

[fr4nc1sc0-r4m0n]

LGTM

[fr4nc1sc0-r4m0n]

buildkite test this