Skip to content

Conversation

@thbkrkr
Copy link
Contributor

@thbkrkr thbkrkr commented Sep 8, 2020

Under unknown conditions, the Kibana telemetry API call may return an empty response and
causes a panic. This commit fixes this by retrying the call until the slice is not empty.

Resolves #3709.

Under unknown conditions, the Kibana telemetry API call may return an empty response and
causes a panic. This commit fixes this by retrying the call until the slice is not empty.
Copy link
Contributor

@sebgl sebgl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lgtm

@anyasabo
Copy link
Contributor

anyasabo commented Sep 8, 2020

Might also be worth opening a kibana issue if non-error responses are always supposed to have a body?

@thbkrkr
Copy link
Contributor Author

thbkrkr commented Sep 9, 2020

Might also be worth opening a kibana issue if non-error responses are always supposed to have a body?

I'm going to reach Kibana folks and see if it's worth opening an issue as I'm not comfortable opening it without being able to repro it.

@thbkrkr
Copy link
Contributor Author

thbkrkr commented Sep 9, 2020

There is a change in the Kibana's startup behaviour that can lead to have /api/status to return green while Kibana is not completely ready. The Beats team encountered this issue (elastic/beats#20772 (comment)). It will soon be fixed (elastic/kibana#76054).

@thbkrkr thbkrkr merged commit f7c02c7 into elastic:master Sep 9, 2020
@thbkrkr thbkrkr deleted the fix-test-telemetry branch October 16, 2020 08:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

TestTelemetry is flaky

4 participants