Switch ESS region to azure-eastus2 for integ tests

[pchila]

What does this PR do?

Why is it important?

Checklist

• [ ] My code follows the style guidelines of this project
• [ ] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [ ] I have made corresponding change to the default configuration files
• [ ] I have added tests that prove my fix is effective or that my feature works
• [ ] I have added an entry in ./changelog/fragments using the changelog tool
• [ ] I have added an integration test or an E2E test

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

Questions to ask yourself

• How are we going to support this in production?
• How are we going to measure its adoption?
• How are we going to debug this?
• What are the metrics I should take care of?
• ...

[mergify]

This pull request does not have a backport label. Could you fix it @pchila? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v./d./d./d is the label to automatically backport to the 8./d branch. /d is the digit

NOTE: backport-skip has been added to this pull request.

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-09-20T15:24:27.962+0000

• Duration: 26 min 7 sec

Test stats 🧪

Test	Results
Failed	0
Passed	6301
Skipped	59
Total	6360

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages.

• run integration tests : Run the Elastic Agent Integration tests.

• run end-to-end tests : Generate the packages and run the E2E Tests.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	98.78% (81/82)	👍
Files	66.327% (195/294)	👍
Classes	65.751% (359/546)	👍
Methods	52.76% (1128/2138)	👍
Lines	38.248% (12814/33502)	👍 0.018
Conditionals	100.0% (0/0)	💚

[elasticmachine]

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

[elastic-sonarqube]

SonarQube Quality Gate

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[blakerouse]

Looks good!

[ycombinator]

Could we add an issue to revert this change and maybe add that issue to the next sprint or something, just so we don't forget about it? Otherwise we'll keep going across data centers between the OGC-provisioned test runner hosts in GCP and ESS deployments in Azure.

And then maybe add a comment here in the code linking to that issue, again, to serve as a reminder?

[pchila]

#3444

[ycombinator]

I think we need to revert this PR and make some fixes to the ESS deployment creation code. Buildkite is failing with this error:

Error: error running test: ogc-linux-arm64-ubuntu-2204-db37 unable to continue because stack never became ready: failed to create ESS cloud for version 8.10.2-SNAPSHOT: failed to create: (cluster.invalid_deployment_template) The referenced deployment template ID [gcp-storage-optimized-v5] does not exist

The gcp-storage-optimized-v5 deployment template cannot be used in Azure. 🤦

[pchila]

@ycombinator I see the error on 8.10 backport but main seems fine... are we missing some commits for the integration test framework ?

[ycombinator]

@ycombinator I see the error on 8.10 backport but main seems fine... are we missing some commits for the integration test framework ?

If main is fine but 8.10 is broken then, yes, it looks like #3365 was missing the backport to 8.10. I see that got taken care of now and the backport for this PR here also got merged successfully. Thanks1