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.

Sign up for GitHub

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

Jump to bottom

Failing test: X-Pack API Integration Tests.x-pack/test/api_integration/apis/management/index_management/indices·js - apis management index management indices list should list all the indices with the expected properties and data enrichers #64473

Closed
kibanamachine opened this issue Apr 25, 2020 · 35 comments · Fixed by #64684, #65575, #99379 or #104155
Closed

Failing test: X-Pack API Integration Tests.x-pack/test/api_integration/apis/management/index_management/indices·js - apis management index management indices list should list all the indices with the expected properties and data enrichers #64473

kibanamachine opened this issue Apr 25, 2020 · 35 comments · Fixed by #64684, #65575, #99379 or #104155
Labels
blocker failed-test A test failure on a tracked branch, potentially flaky-test skipped-test Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more v7.14.0 v8.0.0

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Apr 25, 2020 •
edited
Loading

A test failed on a tracked branch

{ Error: expected [ 'health',
  'status',
  'name',
  'uuid',
  'primary',
  'replica',
  'documents',
  'size',
  'isFrozen',
  'aliases',
  'ilm',
  'isFollowerIndex',
  'isRollupIndex' ] to sort of equal [ 'health',
  'status',
  'name',
  'uuid',
  'primary',
  'replica',
  'documents',
  'size',
  'isFrozen',
  'aliases',
  'isFollowerIndex',
  'ilm',
  'isRollupIndex' ]
    at Assertion.assert (/dev/shm/workspace/kibana/packages/kbn-expect/expect.js:100:11)
    at Assertion.eql (/dev/shm/workspace/kibana/packages/kbn-expect/expect.js:244:8)
    at Context.<anonymous> (test/api_integration/apis/management/index_management/indices.js:201:41)
  actual:
   '[\n  "health"\n  "status"\n  "name"\n  "uuid"\n  "primary"\n  "replica"\n  "documents"\n  "size"\n  "isFrozen"\n  "aliases"\n  "ilm"\n  "isFollowerIndex"\n  "isRollupIndex"\n]',
  expected:
   '[\n  "health"\n  "status"\n  "name"\n  "uuid"\n  "primary"\n  "replica"\n  "documents"\n  "size"\n  "isFrozen"\n  "aliases"\n  "isFollowerIndex"\n  "ilm"\n  "isRollupIndex"\n]',
  showDiff: true }

First failure: Jenkins Build
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Apr 25, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-test-triage (failed-test)

@spalger spalger added the Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more label Apr 25, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/es-ui (Team:Elasticsearch UI)

@spalger
Copy link
Contributor

spalger commented Apr 27, 2020

6 PR failures this week

image

@cjcenizal
Copy link
Contributor

cjcenizal commented Apr 27, 2020 •
edited
Loading

Thanks @spalger. This looks like some sort of race condition between the registration of the index data enrichers. This seems like a benign characteristic, however, because the order in which they're registered doesn't impact the user. So possibly we should solve this by changing the comparison logic in our assertion.

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

spalger added a commit that referenced this issue Apr 30, 2020
@spalger
skip flaky suite (#64473)
c8b9bdd
spalger added a commit that referenced this issue Apr 30, 2020
@spalger
skip flaky suite (#64473)
0cb39e5 
(cherry picked from commit c8b9bdd)
@spalger
Copy link
Contributor

spalger commented Apr 30, 2020

This is failing pretty regularly on master, 7.x, and PRs

image

Skipped

master: c8b9bdd
7.x/7.8: 0cb39e5

@cuff-links cuff-links mentioned this issue May 6, 2020
Merged
@cuff-links
Copy link
Contributor

This was fixed. @spalger Can we get this test re-enabled?

@spalger
Copy link
Contributor

spalger commented May 6, 2020 •
edited
Loading

@cuff-links fixes for flaky tests should include the change to enable the tests, otherwise the fix isn't being tested. Please submit a new PR with the tests re-enabled and run it through the flaky test runner on kibana-ci a handful of times to make sure it's not still flaky.

@cuff-links
Copy link
Contributor

@spalger Gotcha. Will do.

@cuff-links cuff-links mentioned this issue May 6, 2020
Merged
@cuff-links
Copy link
Contributor

This has been merged. Will be backporting.

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine kibanamachine reopened this Feb 8, 2021
@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

brianseeders added a commit that referenced this issue Feb 8, 2021
@brianseeders
skip flaky suite (#64473)
c6fc80c
brianseeders added a commit that referenced this issue Feb 8, 2021
@brianseeders
skip flaky suite (#64473)
82588f1
@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

gmmorris added a commit to gmmorris/kibana that referenced this issue Feb 8, 2021
@gmmorris
Merge branch 'master' into task-manager/support-limited-concurrency
e3c8430 
* master: (55 commits)
  [APM-UI][E2E] use githubNotify step (elastic#90514)
  [APM] Export ProcessorEvent type (elastic#90540)
  [Lens] Retain column config (elastic#90048)
  [Data Table] Add unit tests (elastic#90173)
  Migrate most plugins to synchronous lifecycle (elastic#89562)
  skip flaky suite (elastic#90555)
  skip flaky suite (elastic#64473)
  [actions] improve email action doc (elastic#90020)
  [Fleet] Support Fleet server system indices (elastic#89372)
  skip flaky suite (elastic#90552)
  Bump immer dependencies (elastic#90267)
  Unrevert "Migrations v2: don't auto-create indices + FTR/esArchiver support (elastic#85778)" (elastic#89992)
  [Search Sessions] Use sync config (elastic#90138)
  chore(NA): add safe guard to remove bazelisk from yarn global at bootstrap (elastic#90538)
  [test] Await retry.waitFor (elastic#90456)
  chore(NA): integrate build buddy with our bazel setup and remote cache for ci (elastic#90116)
  Skip failing suite (elastic#90526)
  [Fleet] Fix incorrect conversion of string to numeric values in agent YAML (elastic#90371)
  [Docs] Update reporting troubleshooting for arm rhel/centos (elastic#90385)
  chore(NA): build bazel projects all at once in the distributable build process (elastic#90328)
  ...
mistic pushed a commit that referenced this issue Feb 8, 2021
@brianseeders @mistic
skip flaky suite (#64473)
53bbdad
@cjcenizal
Copy link
Contributor

This is failing consistently because it looks like we're getting back a new data_stream entry in the response. From the logs, we're getting this back:

'[\n' +
    '  "aliases"\n' +
    '  "data_stream"\n' +
    '  "documents"\n' +
    '  "health"\n' +
    '  "hidden"\n' +
    '  "ilm"\n' +
    '  "isFollowerIndex"\n' +
    '  "isFrozen"\n' +
    '  "isRollupIndex"\n' +
    '  "name"\n' +
    '  "primary"\n' +
    '  "replica"\n' +
    '  "size"\n' +
    '  "status"\n' +
    '  "uuid"\n' +
    ']'

Looks like we just need to add data_stream to what we expect:

'[\n' +
    '  "aliases"\n' +
    '  "documents"\n' +
    '  "health"\n' +
    '  "hidden"\n' +
    '  "ilm"\n' +
    '  "isFollowerIndex"\n' +
    '  "isFrozen"\n' +
    '  "isRollupIndex"\n' +
    '  "name"\n' +
    '  "primary"\n' +
    '  "replica"\n' +
    '  "size"\n' +
    '  "status"\n' +
    '  "uuid"\n' +
    ']'

@alisonelizabeth alisonelizabeth mentioned this issue May 5, 2021
Merged
@alisonelizabeth
Copy link
Contributor

The tests are passing for me locally, and I'm not seeing the same error mentioned in #64473 (comment). I've opened a draft PR to rerun via flaky test runner.

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine kibanamachine reopened this Jun 1, 2021
@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

mistic added a commit that referenced this issue Jun 1, 2021
@mistic
skip flaky suite (#64473)
25f569a
mistic added a commit that referenced this issue Jun 1, 2021
@mistic
skip flaky suite (#64473)
7579ce6
@mistic
Copy link
Member

mistic commented Jun 1, 2021 •
edited
Loading

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

master/8.0: 25f569a
7.x/7.14: 7579ce6

@mistic mistic added v7.14.0 and removed v7.12.0 labels Jun 1, 2021
@alisonelizabeth alisonelizabeth mentioned this issue Jul 1, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
blocker failed-test A test failure on a tracked branch, potentially flaky-test skipped-test Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more v7.14.0 v8.0.0
Projects
None yet
Milestone
No milestone
8 participants
@brianseeders @cjcenizal @spalger @cuff-links @mistic @alisonelizabeth @elasticmachine @kibanamachine