Failing test: Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/security/users·ts - security app users edit Deactivate/Activate user deactivates user when confirming

[kibanamachine]

A test failed on a tracked branch

Error: expected true to equal false
    at Assertion.assert (/opt/local-ssd/buildkite/builds/kb-cigroup-6-dbccfa29bbbe05c0/elastic/kibana-hourly/kibana/node_modules/@kbn/expect/expect.js:100:11)
    at Assertion.be.Assertion.equal (/opt/local-ssd/buildkite/builds/kb-cigroup-6-dbccfa29bbbe05c0/elastic/kibana-hourly/kibana/node_modules/@kbn/expect/expect.js:227:8)
    at Assertion.be (/opt/local-ssd/buildkite/builds/kb-cigroup-6-dbccfa29bbbe05c0/elastic/kibana-hourly/kibana/node_modules/@kbn/expect/expect.js:69:22)
    at Context.<anonymous> (test/functional/apps/security/users.ts:206:49)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at Object.apply (/opt/local-ssd/buildkite/builds/kb-cigroup-6-dbccfa29bbbe05c0/elastic/kibana-hourly/kibana/node_modules/@kbn/test/target_node/functional_test_runner/lib/mocha/wrap_function.js:87:16)

First failure: CI Build - 7.16

[kibanamachine]

New failure: CI Build - 8.0

[elasticmachine]

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

[jportner]

Both of the recent failures:

Error: expected true to equal false
    at Assertion.assert (/opt/local-ssd/buildkite/builds/kb-n2-4-2c0b4686fbf8f9e0/elastic/kibana-hourly/kibana/node_modules/@kbn/expect/expect.js:100:11)
    at Assertion.be.Assertion.equal (/opt/local-ssd/buildkite/builds/kb-n2-4-2c0b4686fbf8f9e0/elastic/kibana-hourly/kibana/node_modules/@kbn/expect/expect.js:227:8)
    at Assertion.be (/opt/local-ssd/buildkite/builds/kb-n2-4-2c0b4686fbf8f9e0/elastic/kibana-hourly/kibana/node_modules/@kbn/expect/expect.js:69:22)
    at Context.<anonymous> (test/functional/apps/security/users.ts:208:49)

Screenshot:

The test edits the user, clicks "Deactivate user", confirms the modal, and clicks "Update user" to return to the users page.
The user's Status column should now show a "Disabled" badge, but it doesn't.

Assertion:

kibana/x-pack/test/functional/apps/security/users.ts

Line 208 in 31e9ce7

expect(users.OptionalUser.enabled).to.be(false);

It seems like the user is being updated but we aren't waiting for an index refresh, so we query again too quickly and this is the result.
Since we are using the Elasticsearch API to update a user, we don't have the ability to specify a refresh flag.

I hate to suggest this but it might be prudent to wait for a couple of seconds before we click the "Update user" button to return to the page. WDYT @XavierM ?

[kibanamachine]

New failure: CI Build - main

[kibanamachine]

New failure: CI Build - 7.17

[kibanamachine]

New failure: CI Build - 8.0

[kibanamachine]

New failure: CI Build - main

[mistic]

This test keeps failing and looks flaky. Skipping for now.

main: d296c6f
8.0: f18a138
7.17: 55988cb

[kibanamachine]

New failure: CI Build - 7.17

[kibanamachine]

New failure: CI Build - 7.17

[spalger]

backported skip to 7.17 55988cb

[kibanamachine]

New failure: kibana-on-merge - 8.x

[azasypkin]

Duplicate of #199483 (afterAll that is failing is the same these tests).