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

Failing test: Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/monitoring/kibana/overview·js - Monitoring app Kibana overview "before all" hook for "should have Kibana Cluster Summary Status showing correct info" #72007

Closed
kibanamachine opened this issue Jul 16, 2020 · 7 comments · Fixed by #81200
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:Monitoring Stack Monitoring team

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Jul 16, 2020

A test failed on a tracked branch

Error: retry.try timeout: TimeoutError: Waiting for element to be located By(css selector, [data-test-subj="clusterItemContainerKibana"] [data-test-subj="kbnOverview"])
Wait timed out after 10053ms
    at /dev/shm/workspace/kibana/node_modules/selenium-webdriver/lib/webdriver.js:842:17
    at process._tickCallback (internal/process/next_tick.js:68:7)
    at onFailure (/dev/shm/workspace/kibana/test/common/services/retry/retry_for_success.ts:28:9)
    at retryForSuccess (/dev/shm/workspace/kibana/test/common/services/retry/retry_for_success.ts:68:13)

First failure: Jenkins Build

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Jul 16, 2020
@elasticmachine
Copy link
Contributor

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

@spalger spalger added the Team:Monitoring Stack Monitoring team label Jul 16, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/stack-monitoring (Team:Monitoring)

@spalger
Copy link
Contributor

spalger commented Jul 16, 2020

Two failures in the last week, one on master and one on 7.x, not sure why the master failure isn't logged here.

image

Not skipping for now but request that the monitoring folks look into this before it becomes a problem.

@chrisronline
Copy link
Contributor

Error:

[00:13:45]               │ proc [kibana]   log   [06:30:38.812] [warning][api-authorization][plugins][security] User not authorized for "/api/monitoring/v1/alert/DFDDUmKHR0Ge0mkdYW2bew/status": responding with 404
[00:13:45]               │ proc [kibana]   log   [06:30:38.827] [warning][api-authorization][plugins][security] User not authorized for "/api/monitoring/v1/alerts/enable": responding with 404
[00:13:55]               │ debg --- retry.try error: Waiting for element to be located By(css selector, [data-test-subj="clusterItemContainerKibana"] [data-test-subj="kbnOverview"])
[00:13:55]               │      Wait timed out after 10041ms
[00:13:55]               │ERROR browser[SEVERE] http://localhost:6121/api/monitoring/v1/alert/DFDDUmKHR0Ge0mkdYW2bew/status - Failed to load resource: the server responded with a status of 404 (Not Found)
[00:13:55]               │ERROR browser[SEVERE] http://localhost:6121/api/monitoring/v1/alerts/enable - Failed to load resource: the server responded with a status of 404 (Not Found)
[00:13:55]               │ERROR browser[SEVERE] http://localhost:6121/33347/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js 421:77071 TypeError: Cannot read property 'monitoring_alert_cpu_usage' of undefined
[00:13:55]               │          at http://localhost:6121/33347/bundles/plugin/monitoring/monitoring.chunk.1.js:1:492114
[00:13:55]               │          at Array.find (<anonymous>)

We need to fix this

@chrisronline
Copy link
Contributor

Replaced by #72116

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:Monitoring Stack Monitoring team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants