-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[flakiness]: List agents by hostname and policy id #7012
[flakiness]: List agents by hostname and policy id #7012
Conversation
This pull request does not have a backport label. Could you fix it @pkoutsovasilis? 🙏
|
8a00d06
to
568029e
Compare
4d74041
to
249838e
Compare
buildkite test this |
249838e
to
6821a6c
Compare
buildkite test this |
6821a6c
to
f3090a2
Compare
|
@blakerouse this one addresses the list agents flakiness with a smaller blast radius (no dilemma of whether to retry or not that I introduced 😆 in this PR). The latter is where we wanna go 100% but wdyt of merging this one first to make the CI happy and then work on the other one with some peace of mind? |
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
💚 Build Succeeded
History
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This is a good first iteration for fixing test flakiness before switching to using agentId for querying Fleet about agent status
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This PR improves tests stability. Let's merge it now |
(cherry picked from commit 68aa6d1)
(cherry picked from commit 68aa6d1)
(cherry picked from commit 68aa6d1)
(cherry picked from commit 68aa6d1)
(cherry picked from commit 68aa6d1)
What does this PR do?
This PR re-works how we extract an Agent status from the fleet api and fixes the current issue we have we paginated results.
Why is it important?
It fixes frequent flaky issues that make our CI red
Checklist
./changelog/fragments
using the changelog toolDisruptive User Impact
N/A
How to test this PR locally
Related issues