security test failures

[liza-mae]

- ✖ fail: "security app Security Login Page can login"
│ Error: timed out waiting for logout button visible -- last error: Error: retry.try timeout: ElementClickInterceptedError: element click intercepted: Element ... is not clickable at point (1576, 24). Other element would receive the click:

...
│ (Session info: headless chrome=74.0.3729.108)
│ (Driver info: chromedriver=74.0.3729.6 (255758eccf3d244491b8a1317aa76e1ce10d57e9-refs/branch-heads/3729@{#29}),platform=Linux 4.4.0-142-generic x86_64)
│ at Object.checkLegacyResponse (/home/liza/TESTING/kbn-cloud-testing/node_modules/selenium-webdriver/lib/error.js:585:15)
│ at parseHttpResponse (/home/liza/TESTING/kbn-cloud-testing/node_modules/selenium-webdriver/lib/http.js:533:13)
│ at Executor.execute (/home/liza/TESTING/kbn-cloud-testing/node_modules/selenium-webdriver/lib/http.js:468:26)
│ at process._tickCallback (internal/process/next_tick.js:68:7)
│ at lastError (/home/liza/TESTING/kbn-cloud-testing/test/common/services/retry/retry_for_success.ts:28:9)
│ at onFailure (/home/liza/TESTING/kbn-cloud-testing/test/common/services/retry/retry_for_success.ts:68:13)
│ at onFailure (/home/liza/TESTING/kbn-cloud-testing/test/common/services/retry/retry_for_truthy.ts:50:13)
│ at onFailure (/home/liza/TESTING/kbn-cloud-testing/test/common/services/retry/retry_for_success.ts:68:13)
│
v
✖ fail: "security app dls should add new role myroleEast"
│ Error: expected { a_view_no_ssn_role: { rolename: 'a_view_no_ssn_role', reserved: false },
│ a_viewssnrole: { rolename: 'a_viewssnrole', reserved: false },
│ apm_system: { rolename: 'apm_system', reserved: true },
│ apm_user: { rolename: 'apm_user', reserved: true },
│ beats_admin: { rolename: 'beats_admin', reserved: true },
│ beats_system: { rolename: 'beats_system', reserved: true },
│ code_admin: { rolename: 'code_admin', reserved: true },
│ code_user: { rolename: 'code_user', reserved: true },
│ data_frame_transforms_admin:
│ { rolename: 'data_frame_transforms_admin',
│ reserved: true },
│ data_frame_transforms_user:
│ { rolename: 'data_frame_transforms_user',
│ reserved: true },
│ global_code_all_role: { rolename: 'global_code_all_role', reserved: false },
│ global_code_read_role: { rolename: 'global_code_read_role', reserved: false },
│ ingest_admin: { rolename: 'ingest_admin', reserved: true },
│ kibana_dashboard_only_user:
│ { rolename: 'kibana_dashboard_only_user',
│ reserved: true },
│ kibana_system: { rolename: 'kibana_system', reserved: true },
│ kibana_user: { rolename: 'kibana_user', reserved: true },
│ 'logstash-data': { rolename: 'logstash-data', reserved: false },
│ 'logstash-readonly': { rolename: 'logstash-readonly', reserved: false },
│ logstash_admin: { rolename: 'logstash_admin', reserved: true },
│ logstash_reader: { rolename: 'logstash_reader', reserved: false } } to include key 'myroleEast'
│ at Assertion.assert (/home/liza/TESTING/kbn-cloud-testing/packages/kbn-expect/expect.js:100:11)
│ at Assertion.key.Assertion.keys (/home/liza/TESTING/kbn-cloud-testing/packages/kbn-expect/expect.js:478:8)
│ at Context.key (test/functional/apps/security/doc_level_security_roles.js:50:29)
│

✖ fail: "security app Management Security navigation Can navigate to edit role section"
│ Error: retry.try timeout: TimeoutError: Waiting for element to be located By(link text, my-new-role)
│ Wait timed out after 10029ms
│ at /home/liza/TESTING/kbn-cloud-testing/node_modules/selenium-webdriver/lib/webdriver.js:834:17
│ at process._tickCallback (internal/process/next_tick.js:68:7)
│ at lastError (/home/liza/TESTING/kbn-cloud-testing/test/common/services/retry/retry_for_success.ts:28:9)
│ at onFailure (/home/liza/TESTING/kbn-cloud-testing/test/common/services/retry/retry_for_success.ts:68:13)

✖ fail: "security app users should show the default roles"
│ TypeError: Cannot read property 'reserved' of undefined
│ at Context.reserved (test/functional/apps/security/users.js:81:36)

Version: 7.2

[elasticmachine]

Pinging @elastic/kibana-security

[elasticmachine]

Pinging @elastic/kibana-test-triage

[liza-mae]

Failures are related to #39689

[legrego]

@liza-mae do you think we can safely close this issue, since these failures were related to #39689, which itself been resolved?

[liza-mae]

Yes we can close.