Skip to content
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

[Fleet] Kibana cannot start (so e2e test times out connecting to ES) #89489

Closed
EricDavisX opened this issue Jan 27, 2021 · 6 comments
Closed
Labels
bug Fixes for quality problems that affect the customer experience

Comments

@EricDavisX
Copy link
Contributor

Kibana 8.0 snapshot latest version as of Jan 27 afternoon. Manu reports the tests this morning were working... started failing around 10 AM EST

working, earlier test: https://beats-ci.elastic.co/blue/organizations/jenkins/e2e-tests%2Fe2e-testing-mbp/detail/PR-669/5/pipeline
hours later today: https://beats-ci.elastic.co/blue/organizations/jenkins/e2e-tests%2Fe2e-testing-mbp/detail/PR-669/7/pipeline

Original install method (e.g. download page, yum, from source, etc.):
snapshots / obs ci-snapshots

Steps to reproduce:
run the e2e-test and see the cited problem

Expected behavior:
test passes : /

Errors in browser console (if relevant):
{"type":"log","@timestamp":"2021-01-27T19:34:42+00:00","tags":["warning","plugins","licensing"],"pid":8,"message":"License information could not be obtained from Elasticsearch due to Error: Cluster client cannot be used after it has been closed. error"}

Provide logs and/or server output (if relevant):
Nicolas Chaulet cites: also there is a change to the saved object migration that has been merged today can be related

he notes this from the following, the line migration failed, dumping execution
...seems like there is a migration issue somewhere

full log:
kibana-logs.log

@EricDavisX EricDavisX added bug Fixes for quality problems that affect the customer experience Team:Fleet Team label for Observability Data Collection Fleet team labels Jan 27, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/ingest-management (Team:Ingest Management)

@EricDavisX
Copy link
Contributor Author

@mdelapenya thanks for raising this. @ph it is going to block our e2e tests until it is solved.

@mdelapenya
Copy link
Contributor

Just to mention, kibana is not even starting before any test runs. Running latest kibana and Elasticsearch 8.0.0-SNAPSHOT would be enough to reproduce. We have a custom kibana config in the e2e-testing repository that could affect.

@EricDavisX EricDavisX changed the title [Fleet] Kibana problem responding to Agent / Endpoint requests, so it times out (and in our use case, e2e tests fail) [Fleet] Kibana cannot start (so e2e test times out connecting to ES) Jan 27, 2021
@EricDavisX
Copy link
Contributor Author

keep in mind after we get Kibana started we still likely should expect tests to fail, as they were before the overall-Kibana failure: elastic/beats#23693

@EricDavisX
Copy link
Contributor Author

this pr should fix Kibana and we'll be back to following up on existing bugs on Fleet / Agent / e2e-testing side:
#89541

@EricDavisX EricDavisX removed the Team:Fleet Team label for Observability Data Collection Fleet team label Jan 28, 2021
@EricDavisX
Copy link
Contributor Author

this is taken care of so I am closing out - Kibana on 8.0 is working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience
Projects
None yet
Development

No branches or pull requests

3 participants