-
Notifications
You must be signed in to change notification settings - Fork 143
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
[Flaky Test] Integration/e2e tests installing the agent randomly fail #3154
Labels
Comments
AndersonQ
added
flaky-test
Unstable or unreliable test cases.
Team:Elastic-Agent
Label for the Agent team
labels
Jul 31, 2023
Pinging @elastic/elastic-agent (Team:Elastic-Agent) |
Going to skip these tests while we investigate the root cause: #3164 |
cmacknz
added a commit
that referenced
this issue
Aug 1, 2023
All of the proxy tests are currently flaky and fail regularly, see #3154 Disabling them while we investigate a fix to unblock CI.
1 task
AndersonQ
pushed a commit
that referenced
this issue
Aug 16, 2023
All of the proxy tests are currently flaky and fail regularly, see #3154 Disabling them while we investigate a fix to unblock CI.
AndersonQ
added a commit
that referenced
this issue
Aug 16, 2023
…roxy-url integration test and disable tests (#3147) * enhance mock fleet-server and add --proxy-url integration test (#2834) * enhance test fleet-server Now a almost fully functional mock fleet-server can be instantiated with a single call to fleetservertest.NewServerWithHandlers. The only missing handlers are the upload handlers. testing/integration/proxy_url_test.go works as example on how to use the new features of the test fleet-server * add proxytest.Proxy: A naive proxy to be used on tests which allows to configure URL rewrites and check all the calls made to it. check the tests on testing/integration/proxy_url_test.go to see how to use proxytest.Proxy. * add integration tests for the fleet-server proxy The tests cover defining a proxy through --proxy-url and in the policy and the correct priority is respected * fix the Go version used on the Github workflows now it reads the version from the .go-version and not from the go.mod anymore. * increase the memory allocated to the elastic-agent vagrant box * allow -SNAPHOT versions to be passed to define.NewFixture * add more helper methods to testing.Fixture and Install accepts more flags * add version.Agent, a exported constant with the agent version (cherry picked from commit 732d7c0) * Disable proxy tests while flakiness is addressed. (#3164) All of the proxy tests are currently flaky and fail regularly, see #3154 Disabling them while we investigate a fix to unblock CI. (cherry picked from commit 08d24b9) --------- Co-authored-by: Anderson Queiroz <[email protected]> Co-authored-by: Craig MacKenzie <[email protected]>
This was referenced Aug 16, 2023
closed by #3240 |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Flaky Test
Notes
testify/suite
with SetUp/TearDown as the ProxyURL test do not use it, and other failing tests usetestify/suite
.Once I spotted this issue while running the tests on a Vagrant box, and I managed to gather the following:
The agent reported not enrolled into fleet, however it did call /enroll and the request succeeded.
in the test logs I can see the call to fleet through the proxy:
the agent stat.yaml:
there is just one log file, from the agent startup, not from the install process, and it says the agent is managed locally:
for this specific case, the agent started not enrolled in fleet. Which should not happen at all. The same might be happening for all instances when the test fails.
Stack Trace
The text was updated successfully, but these errors were encountered: