-
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: X-Pack Usage Collection Functional Tests.x-pack/test/usage_collection/test_suites/application_usage - Application Usage keys in the schema match the registered application IDs #90536
Comments
New failure: Jenkins Build |
Pinging @elastic/kibana-telemetry (Team:KibanaTelemetry) |
New failure: Jenkins Build |
New failure: Jenkins Build |
Yesterday's failures, both of them are related to Kibana failing to validate the licensing info when navigating to the
Not related to Application Usage as such. I'll update the test to reflect errors others than the actual schema check. |
Nevermind, I noticed that we show the same error even in the successful runs. Digging further into this. |
Found the bug! The tests are navigating to |
Pinging @elastic/kibana-core (Team:Core) |
New failure: CI Build - master |
do you mean that the components changed and that we need to change that check again? |
New failure: CI Build - main |
New failure: CI Build - main |
New failure: CI Build - main |
New failure: CI Build - main |
New failure: CI Build - main |
Temporary failure that was caused by unrelated PR and resolved later. The issue can be safely closed. |
New failure: kibana-on-merge - main |
It looks like |
New failure: kibana-on-merge - main |
Maybe the license fetching system is flaky in the test? I can see that this app is only registered if a certain level of the license is met:
I'll close this issue for now because it hasn't happened in 2 days. But we might want to investigate that license issue if it happens again. |
New failure: kibana-elasticsearch-snapshot-verify - main |
Again @elastic/search-kibana, are you aware of any flakiness in the app not being registered sometimes? |
@afharo yes we've had issues with the way that app is registered since the license check is async, we have an outstanding bug that we think could be caused by how it's registered as well. We are investigating refactoring the app registration to use a KibanaFeature for license gating instead of doing a manual license check. But I'm not sure what the timeline on that is. cc: @saikatsarkar056 |
@afharo tangentially I think we have a few other apps we might need to add to |
oh! that's a good point and I think it highlights a flaw in this test: it runs with the default Kibana configuration instead of enabling all plugins. It's not a blocker, since the schema is mostly for documentation purposes and validation. But we may need to look at refactoring this test to find all potentially registered apps (maybe AST instead of a runtime test?). I created #191059 to tackle that rewrite. |
A test failed on a tracked branch
First failure: Jenkins Build
The text was updated successfully, but these errors were encountered: