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 Security Functional Tests (Login Selector).x-pack/test/security_functional/tests/login_selector/basic_functionality·ts - security app - login selector Basic functionality can login after Unauthorized error during request authentication preserving original URL #98562

Closed
kibanamachine opened this issue Apr 27, 2021 · 11 comments · Fixed by #106822 or #119715
Assignees
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Apr 27, 2021

A test failed on a tracked branch

Error: retry.try timeout: Error: retry.try timeout: TimeoutError: Waiting for element to be located By(css selector, [data-test-subj="loginErrorMessage"])
Wait timed out after 10026ms
    at /dev/shm/workspace/parallel/17/kibana/node_modules/selenium-webdriver/lib/webdriver.js:842:17
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at onFailure (/dev/shm/workspace/parallel/17/kibana/test/common/services/retry/retry_for_success.ts:17:9)
    at retryForSuccess (/dev/shm/workspace/parallel/17/kibana/test/common/services/retry/retry_for_success.ts:57:13)
    at Retry.try (/dev/shm/workspace/parallel/17/kibana/test/common/services/retry/retry.ts:32:14)
    at /dev/shm/workspace/parallel/17/kibana/x-pack/test/functional/page_objects/security_page.ts:146:39
    at runAttempt (/dev/shm/workspace/parallel/17/kibana/test/common/services/retry/retry_for_success.ts:27:15)
    at retryForSuccess (/dev/shm/workspace/parallel/17/kibana/test/common/services/retry/retry_for_success.ts:66:21)
    at Retry.try (/dev/shm/workspace/parallel/17/kibana/test/common/services/retry/retry.ts:32:14)
    at Object.getErrorMessage (test/functional/page_objects/security_page.ts:145:14)
    at Context.<anonymous> (test/security_functional/tests/login_selector/basic_functionality.ts:146:14)
    at Object.apply (/dev/shm/workspace/parallel/17/kibana/node_modules/@kbn/test/src/functional_test_runner/lib/mocha/wrap_function.js:73:16)
    at onFailure (/dev/shm/workspace/parallel/17/kibana/test/common/services/retry/retry_for_success.ts:17:9)
    at retryForSuccess (/dev/shm/workspace/parallel/17/kibana/test/common/services/retry/retry_for_success.ts:57:13)
    at Retry.try (/dev/shm/workspace/parallel/17/kibana/test/common/services/retry/retry.ts:32:14)
    at Object.getErrorMessage (test/functional/page_objects/security_page.ts:145:14)
    at Context.<anonymous> (test/security_functional/tests/login_selector/basic_functionality.ts:146:14)
    at Object.apply (/dev/shm/workspace/parallel/17/kibana/node_modules/@kbn/test/src/functional_test_runner/lib/mocha/wrap_function.js:73:16)

First failure: Jenkins Build

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Apr 27, 2021
@botelastic botelastic bot added the needs-team Issues missing a team label label Apr 27, 2021
@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@tylersmalley
Copy link
Contributor

tylersmalley commented Apr 28, 2021

Skipped

image

7.x: b52b032
master/8.0: 9a6c774
7.16: b3046e0

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

mistic added a commit that referenced this issue May 4, 2021
@mistic mistic added v8.0.0 Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more! and removed v7.14.0 labels May 4, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-security (Team:Security)

@botelastic botelastic bot removed the needs-team Issues missing a team label label May 4, 2021
@legrego
Copy link
Member

legrego commented May 4, 2021

@azasypkin I think this one is related to the improved 401 handling that we recently merged. Would you mind taking a look at this when you get a chance?

@azasypkin
Copy link
Member

@azasypkin I think this one is related to the improved 401 handling that we recently merged. Would you mind taking a look at this when you get a chance?

Sure, thanks for the ping!

@azasypkin
Copy link
Member

I found the root cause, but not sure how to fix that yet. Between the moment when we disable current user (to simulate error in the authentication pipeline) and the moment when we refresh current page Kibana sends a number of API requests that fail with 401 and client side interceptor forces logout right before WebDriver refreshes page.

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - 7.16

tylersmalley pushed a commit that referenced this issue Nov 10, 2021
@azasypkin
Copy link
Member

It seems the test fails on 7.16 only (for now). We used flaky test runner only on main, let's see if flaky test runner can detect this issue on 7.16.

https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/193

@azasypkin
Copy link
Member

No luck, CI and Flaky Test runner are completely happy. Will try to figure this out.

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:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!
Projects
None yet
6 participants