[9.1][Automation] Bump VM Image version to 1764775167

[github-actions]

Bump vm-images to latest version

Update .buildkite/bk.integration.pipeline.yml

1 file(s) updated with "$1: \"platform-ingest-elastic-agent-$2-1764775167\"": * .buildkite/bk.integration.pipeline.yml

Update .buildkite/pipeline.elastic-agent-binary-dra.yml

1 file(s) updated with "$1: \"platform-ingest-elastic-agent-$2-1764775167\"": * .buildkite/pipeline.elastic-agent-binary-dra.yml

Update .buildkite/pipeline.yml

1 file(s) updated with "$1: \"platform-ingest-elastic-agent-$2-1764775167\"": * .buildkite/pipeline.yml

Update .buildkite/bk.integration-fips.pipeline.yml

1 file(s) updated with "$1: \"platform-ingest-elastic-agent-$2-1764775167\"": * .buildkite/bk.integration-fips.pipeline.yml

Update .buildkite/integration.pipeline.yml

1 file(s) updated with "$1: \"platform-ingest-elastic-agent-$2-1764775167\"": * .buildkite/integration.pipeline.yml

Update .buildkite/pipeline.elastic-agent-package.yml

1 file(s) updated with "$1: \"platform-ingest-elastic-agent-$2-1764775167\"": * .buildkite/pipeline.elastic-agent-package.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!

[mergify]

Automatically approving mergify

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 9cdfce8

[mergify]

Merge Queue Status

🚫 The pull request has left the queue (rule: default)

This pull request spent 55 minutes 31 seconds in the queue, with no time running CI.
The checks were run on draft #11654.

Required conditions to merge

• check-success=buildkite/elastic-agent
• any of [🛡 GitHub branch protection]:
  • check-neutral = buildkite/elastic-agent
  • check-skipped = buildkite/elastic-agent
  • check-success = buildkite/elastic-agent
• #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule]
  • [9.1][Automation] Bump VM Image version to 1764775167 #11652
• #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule]
  • [9.1][Automation] Bump VM Image version to 1764775167 #11652
• #changes-requested-reviews-by = 0 [🛡 GitHub repository ruleset rule]
  • [9.1][Automation] Bump VM Image version to 1764775167 #11652
• #changes-requested-reviews-by = 0 [🛡 GitHub repository ruleset rule]
  • [9.1][Automation] Bump VM Image version to 1764775167 #11652
• #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • [9.1][Automation] Bump VM Image version to 1764775167 #11652
• check-success=CLA
• any of [🛡 GitHub branch protection]:
  • check-success = CLA
  • check-neutral = CLA
  • check-skipped = CLA

Reason

Pull request #11652 has been dequeued. The pull request has been closed manually

Hint

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.