[test-failed]: Chrome UI Functional Tests1.test/functional/apps/dashboard/bwc_shared_urls·js.dashboard app using legacy data bwc shared urls 6.0 urls loads an unsaved dashboard

[liza-mae]

Version: 7.9.0, 8.0.0 Snapshots
Class: Chrome UI Functional Tests1.test/functional/apps/dashboard/bwc_shared_urls·js
Stack Trace:
Error: retry.try timeout: TimeoutError: Waiting for element to be located By(css selector, [data-test-subj="queryInput"])
Wait timed out after 10018ms
at /var/lib/jenkins/workspace/elastic+estf-cloud-kibana-tests/JOB/ossGrp3/TASK/saas_run_kibana_tests/node/linux-immutable/ci/cloud/common/build/kibana/node_modules/selenium-webdriver/lib/webdriver.js:842:17
at process._tickCallback (internal/process/next_tick.js:68:7)
at onFailure (test/common/services/retry/retry_for_success.ts:28:9)
at retryForSuccess (test/common/services/retry/retry_for_success.ts:68:13
Platform: cloud
Build Num: 453

[elasticmachine]

Pinging @elastic/kibana-test-triage (failed-test)

[elasticmachine]

Pinging @elastic/kibana-app (Team:KibanaApp)

[liza-mae]

There are multiple failures

• dashboard app using legacy data bwc shared urls 6_0 urls loads a saved dashboard
• dashboard app using legacy data bwc shared urls 6_0 urls uiState in url takes precedence over saved dashboard state
• dashboard app using current data legacy urls kibana link redirect redirects from old kibana app URL
• dashboard app using legacy data bwc shared urls 6_0 urls loads an unsaved dashboard
• dashboard app using legacy data bwc shared urls 6_0 urls back button works for old dashboards after state migrations
• dashboard app using legacy data bwc shared urls 5_6 urls url with filters and query

[liza-mae]

I noticed these tests are coming back with application not found errors and wanted to make sure it is not a real issue. If someone can confirm? Thanks.

[timroes]

@flash1293 this seems like it could be a potentially failure actually related to the split up of the kibana plugin?

[liza-mae]

Since this is happening on 7.9.0 BC1 - it should be looked at before we release.

[flash1293]

I'm checking it out this week

[flash1293]

OK, so this is a permission problem, we should definitely fix it for 7.9

It seems like the kibana_admin user has no permissions to access the kibana app anymore. I'm not sure how this can be, as it has "All" privileges on the default space and most of the features in there (discover, visualize, dashboard, ...) implicitly grant access to the kibana app as well. @legrego could you help here? I think for permissions we should just make kibana accessible by everyone.

https://github.com/flash1293/kibana/blob/28b70923df4411431fcc625f1fa0e8e8d321aec4/x-pack/plugins/features/server/oss_features.ts#L84

[legrego]

Yeah this was a regression caused by #71106. I'll have a PR up today to resolve this

[flash1293]

Great, thanks @legrego ! And thanks to @liza-mae for the cloud tests, this would have been in 7.9.1 otherwise :)

[liza-mae]

Thanks @legrego and @flash1293 for your prompt attention and fix ! :)

[legrego]

Great catch, Thanks @liza-mae for catching this with the cloud test!

@flash1293 is there a way for us to update this test to run using the kibana_admin user for CI, instead of waiting for cloud to discover this failure?

[flash1293]

@legrego That's not super easy because this specific test is part of the OSS test suite, this means in CI they run without x-pack. I don't think we can simply switch that to always run with x-pack as we would have the same problem in the other direction (no CI tests for OSS anymore). We could probably run the whole OSS test suite as kibana_admin in addition to the current setup, but that seems expensive to me - I'll leave this question to @elastic/kibana-qa .