Failing test: Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/remote_clusters/feature_controls/remote_clusters_security·ts - Remote Clusters app feature controls security global dashboard read with license_management_user should render the "Data" section with Remote Clusters

[kibanamachine]

A test failed on a tracked branch

Error: expected [ { sectionId: 'ingest',
    sectionLinks: [ 'ingest_pipelines', 'pipelines' ] },
  { sectionId: 'data',
    sectionLinks: 
     [ 'index_management',
       'index_lifecycle_management',
       'snapshot_restore',
       'rollup_jobs',
       'transform',
       'remote_clusters' ] },
  { sectionId: 'insightsAndAlerting',
    sectionLinks: [ 'watcher' ] },
  { sectionId: 'stack',
    sectionLinks: [ 'license_management', 'upgrade_assistant' ] } ] to have a length of 3 but got 4
    at Assertion.assert (/dev/shm/workspace/parallel/24/kibana/packages/kbn-expect/expect.js:100:11)
    at Assertion.length (/dev/shm/workspace/parallel/24/kibana/packages/kbn-expect/expect.js:374:8)
    at Context.<anonymous> (test/functional/apps/remote_clusters/feature_controls/remote_clusters_security.ts:66:34)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at Object.apply (/dev/shm/workspace/parallel/24/kibana/packages/kbn-test/src/functional_test_runner/lib/mocha/wrap_function.js:73:16)

First failure: Jenkins Build

[elasticmachine]

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

[gmmorris]

@elastic/kibana-security I've tagged you as I think this is yours. 😬
Sorry if I got that wrong

[legrego]

@gmmorris for future reference, @elastic/kibana-security only owns security-related tests that are associated with security plugins (and saved objects, just because 😄).

Security-related tests that verify functionality of specific applications or solutions are owned by the respective app/solution teams. It's very possible that we were the original authors, but the responsibility lies with the app/solution teams going forward.

All that said, this looks like something I'll have resolved as part of #92694