Update all usages of fleettools to use the installed Agent ID

[blakerouse]

What does this PR do?

Updates all integration tests to use the installed Elastic Agent ID from the status output to check with Fleet for information about the specific Elastic Agent.

Why is it important?

This ensures that the tests in the integration framework are only communicating with Fleet about that specific Elastic Agent. This removes the need to filter based on hostname or doing any type of paging with the Kibana API to find that specific Elastic Agent. We know the Elastic Agent ID as the test installed it, it should always use that ID.

Checklist

• I have read and understood the pull request guidelines of this project.
• 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 (all integration tests)
• [ ] I have added an entry in ./changelog/fragments using the changelog tool (testing only)
• I have added an integration test or an E2E test

Disruptive User Impact

None

How to test this PR locally

mage integration:test

Related issues

• Closes [Flaky Test]: TestFleetAirGappedUpgradeUnprivileged – Agent status is not online #6968
• Closes [Flaky Test]: TestFleetAirGappedUpgradePrivileged – Agent status is not online #6924

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?
• ...

[elasticmachine]

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

[jlind23]

There were cloud instability while creating deployment, restarting tests.

[blakerouse]

buildkite test this

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b integration-use-agent-id-with-fleet upstream/integration-use-agent-id-with-fleet
git merge upstream/main
git push upstream integration-use-agent-id-with-fleet

[pkoutsovasilis]

until we discuss with the team about what DRY is and when to try to perform it and what developers of integration tests should seek out and all of us collectively agree to a definition, I believe that this PR should not be merged

[blakerouse]

until we discuss with the team about what DRY is and when to try to perform it and what developers of integration tests should seek out and all of us collectively agree to a definition, I believe that this PR should not be merged

Happy to discuss.

[blakerouse]

I am working on cleaning this up more from @cmacknz comments to have the install functions return the agent ID, that way its clear what the Agent ID is from the installation with enrollment step. Placing back in draft while I do this.

[elasticmachine]

⏳ Build in-progress, with failures

• Buildkite Build
• Commit: c92ece7

Failed CI Steps

• Unit tests - Windows 2022
• Unit tests - Windows 2022
• Serverless integration test
• Extended runtime leak tests
• Extended runtime leak tests
• Win2022:sudo:default
• Win2022:sudo:default
• Win2022:sudo:fleet
• Win2022:sudo:fleet-endpoint-security
• Win2025:sudo:default
• Win2025:sudo:default
• Win2025:sudo:fleet
• Win2025:sudo:fleet-endpoint-security
• x86_64:sudo: default
• x86_64:sudo: default
• x86_64:sudo: fleet
• x86_64:sudo: fleet-endpoint-security
• x86_64:sudo: deb
• arm:sudo: default
• arm:sudo: default
• arm:sudo: fleet
• x86_64:sudo:rpm

History

• 💛 Build #18136 was flaky 411d8b6
• 💚 Build #17814 succeeded 6561c3c
• 💔 Build #17786 failed bd56d4e
• 💔 Build #17778 failed fdd8912

cc @blakerouse

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube