-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Failing test: Package testing.assert_kibana_available : localhost:5601/api/status #106749
Comments
Pinging @elastic/kibana-operations (Team:Operations) |
Hi @jbudz I would like to bring some more attention to this issue because it seems quite similar to one that we're seeing. This may be a problem which is actually affecting other teams in Elastic. For example, in Observability, we run APM Integration Tests which have been failing quite frequently as a result of the status API not being available after the Kibana container starts. We even raised our timeout to wait for this API in Kibana to 5 minutes and we're still seeing the same timeouts. If we can't reliably count on Kibana to give us a signal that it has started successfully, this is quite problematic for the orchestration that our entire integration testing platform depends on. A few questions:
We're definitely happy to continue providing any information that can help get this fixed, but we'd also like to see what could possibly be done about prioritizing a fix for this. Though it's certainly not a high-priority for end users (probably?) it's definitely having a negative impact on our ability to deliver reliable testing for our teams. Thanks in advance! cc: @elastic/observablt-robots |
This is the logs of the running @cachedout is talking about, there are no logs after 2021-07-29T03:24:35+00:00, we wait 5 min for kibana checking the
|
@jbudz @tylersmalley Could you please provide the status of this? Thank you |
@cachedout, thanks for the information. I am not aware of this issue, but |
Thanks for the reply @tylersmalley . I wasn't sure if a new issue was better since it seemed like it would be a duplicate of this one. I'll go ahead and take what's here and put it into a new issue for the core folks to look at. |
@cachedout, this issue is just to track that we have disabled the test in our package testing. We have yet to investigate a cause, which very well could be the issue you have described. In regards to if hitting the status endpoint is the right approach to determine if Kibana is up. I know a common practice for load balancer configurations with Kibana is to hit the root |
Thanks @tylersmalley . I agree that filing an issue would have been a better approach. Apologies for not doing that originally. I've filed the new issue here: #107300 (I'll also move your comment re: the |
The socket timeout for testing whether the status page is available or not is currently 30 seconds. This test was disabled for being flaky. Reproducing this locally hasn't been straight forward, but I am seeing an average of ~20 seconds, which is close enough to the timeout that I'd like to rule out machine differences. This gives the status check 120 seconds before dropping the connection. Related to elastic#106749 and elastic#107300
The socket timeout for testing whether the status page is available or not is currently 30 seconds. This test was disabled for being flaky. Reproducing this locally hasn't been straight forward, but I am seeing an average of ~20 seconds, which is close enough to the timeout that I'd like to rule out machine differences. This gives the status check 120 seconds before dropping the connection. Related to #106749 and #107300 Co-authored-by: Kibana Machine <[email protected]>
The socket timeout for testing whether the status page is available or not is currently 30 seconds. This test was disabled for being flaky. Reproducing this locally hasn't been straight forward, but I am seeing an average of ~20 seconds, which is close enough to the timeout that I'd like to rule out machine differences. This gives the status check 120 seconds before dropping the connection. Related to elastic#106749 and elastic#107300 Co-authored-by: Kibana Machine <[email protected]>
The socket timeout for testing whether the status page is available or not is currently 30 seconds. This test was disabled for being flaky. Reproducing this locally hasn't been straight forward, but I am seeing an average of ~20 seconds, which is close enough to the timeout that I'd like to rule out machine differences. This gives the status check 120 seconds before dropping the connection. Related to #106749 and #107300 Co-authored-by: Kibana Machine <[email protected]> Co-authored-by: Jonathan Budzenski <[email protected]>
Resolved by #107813 |
https://kibana-ci.elastic.co/job/elastic+kibana+package-testing-7.x/43
https://kibana-ci.elastic.co/job/elastic+kibana+package-testing/57
The text was updated successfully, but these errors were encountered: