Open kibanamachine opened 1 year ago
Pinging @elastic/kibana-security (Team:Security)
I'll wait a bit more to see how frequent this failure is. If it fails again, we might use the same approach we use in the concurrent sessions tests instead.
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - main
/skip
Skipped
main: fc9a63118c86657a9eab1c7a1f81f5e794498522
New failure: CI Build - 8.8
New failure: CI Build - 8.8
Ran another flaky test runner just to be sure, but this looks tied to a series of CI failures on Friday.
New failure: kibana-elasticsearch-snapshot-verify - 8.14
proc [kibana] [2024-06-18T14:18:23.761+00:00][ERROR][plugins.security.saml.saml_override] Failed to log in with SAML response: {"error":{"root_cause":[{"type":"security_exception","reason":"error attempting to authenticate request","header":{"WWW-Authenticate":["Basic realm=\"security\" charset=\"UTF-8\"","Bearer realm=\"security\"","ApiKey"]}}],"type":"security_exception","reason":"error attempting to authenticate request","caused_by":{"type":"array_index_out_of_bounds_exception","reason":"Index 1 out of bounds for length 0"},"header":{"WWW-Authenticate":["Basic realm=\"security\" charset=\"UTF-8\"","Bearer realm=\"security\"","ApiKey"]}},"status":401} {"service":{"node":{"roles":["background_tasks","ui"]}}} [00:00:47] │
This one caused by some mysterious error in ES that should not happen in theory and we couldn't reproduce it either. Closing for now.
New failure: kibana-on-merge - main
New failure: kibana-on-merge - main
@SiddharthMantri do you think we can turn on the ES trace logs for the session_idle
, session_invalidate
, and session_concurrent_limit
test suites as well, like you did for session_lifespan
? The underlying issue (a bug in ES) seems to be what's causing these tests to fail as well.
@azasypkin Missed the ping last week. Just opened a PR here: https://github.com/elastic/kibana/pull/193259
A test failed on a tracked branch
First failure: CI Build - 8.7