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/data_streams·ts - management index management Data streams Get index mode index mode of logs-*-* data streams returns standard index mode if logsdb.enabled setting is null #209014

Open
kibanamachine opened this issue Jan 30, 2025 · 13 comments · Fixed by #209102
Open

Failing test: X-Pack API Integration Tests.x-pack/test/api_integration/apis/management/index_management/data_streams·ts - management index management Data streams Get index mode index mode of logs-*-* data streams returns standard index mode if logsdb.enabled setting is null #209014

kibanamachine opened this issue Jan 30, 2025 · 13 comments · Fixed by #209102
Assignees
@ElenaStoeva
Labels
failed-es-promotion failed-test A test failure on a tracked branch, potentially flaky-test Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Jan 30, 2025 •
edited
Loading

A test failed on a tracked branch

Error: expected 'logsdb' to sort of equal 'standard'
    at Assertion.assert (expect.js:100:11)
    at Assertion.eql (expect.js:244:8)
    at Context.<anonymous> (data_streams.ts:221:47)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Object.apply (wrap_function.js:74:16) {
  actual: 'logsdb',
  expected: 'standard',
  showDiff: true
}

First failure: kibana-elasticsearch-snapshot-verify - 9.0
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Jan 30, 2025
@botelastic botelastic bot added the needs-team Issues missing a team label label Jan 30, 2025
@kibanamachine kibanamachine added failed-es-promotion Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more labels Jan 30, 2025
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-management (Team:Kibana Management)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 30, 2025
@kibanamachine
Copy link
Contributor Author

New failure: kibana-elasticsearch-snapshot-verify - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-elasticsearch-snapshot-verify - 9.0

@kibanamachine
Copy link
Contributor Author

New failure: kibana-elasticsearch-snapshot-verify - main

kibanamachine added a commit that referenced this issue Jan 30, 2025
@kibanamachine
skip failing test suite (#209014)
597c0ea
@kibanamachine
Copy link
Contributor Author

Skipped

9.0: 597c0ea
main: 970d805

kibanamachine added a commit that referenced this issue Jan 30, 2025
@kibanamachine
skip failing test suite (#209014)
970d805
@mistic mistic added the v9.1.0 label Jan 30, 2025
@ElenaStoeva ElenaStoeva mentioned this issue Jan 31, 2025
Merged
ElenaStoeva added a commit that referenced this issue Feb 3, 2025
@ElenaStoeva
[Data Streams] Unskip API integration tests (#209102)
96e3d55 
Closes #209014

## Summary

This PR unskips and updates the Data streams API integration tests to
reflect the recent changes to Elasticsearch
(elastic/elasticsearch#121049). Previously, the
`cluster.logsdb.enabled` setting was always `false` by default in
stateful Kibana. With the new changes, it is `true` by default if the
`logsdb.prior_logs_usage` setting is `false` (which is the case for new
test clusters, hence the test failure), and `true` otherwise. Therefore,
we need to update the tests so that we test both cases.

Flaky test runner:
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7821
kibanamachine pushed a commit to kibanamachine/kibana that referenced this issue Feb 3, 2025
@ElenaStoeva
[Data Streams] Unskip API integration tests (elastic#209102)
13fbae5 
Closes elastic#209014

## Summary

This PR unskips and updates the Data streams API integration tests to
reflect the recent changes to Elasticsearch
(elastic/elasticsearch#121049). Previously, the
`cluster.logsdb.enabled` setting was always `false` by default in
stateful Kibana. With the new changes, it is `true` by default if the
`logsdb.prior_logs_usage` setting is `false` (which is the case for new
test clusters, hence the test failure), and `true` otherwise. Therefore,
we need to update the tests so that we test both cases.

Flaky test runner:
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7821

(cherry picked from commit 96e3d55)
kibanamachine pushed a commit to kibanamachine/kibana that referenced this issue Feb 3, 2025
@ElenaStoeva
[Data Streams] Unskip API integration tests (elastic#209102)
61adada 
Closes elastic#209014

## Summary

This PR unskips and updates the Data streams API integration tests to
reflect the recent changes to Elasticsearch
(elastic/elasticsearch#121049). Previously, the
`cluster.logsdb.enabled` setting was always `false` by default in
stateful Kibana. With the new changes, it is `true` by default if the
`logsdb.prior_logs_usage` setting is `false` (which is the case for new
test clusters, hence the test failure), and `true` otherwise. Therefore,
we need to update the tests so that we test both cases.

Flaky test runner:
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7821

(cherry picked from commit 96e3d55)
kibanamachine pushed a commit to kibanamachine/kibana that referenced this issue Feb 3, 2025
@ElenaStoeva
[Data Streams] Unskip API integration tests (elastic#209102)
b83335d 
Closes elastic#209014

## Summary

This PR unskips and updates the Data streams API integration tests to
reflect the recent changes to Elasticsearch
(elastic/elasticsearch#121049). Previously, the
`cluster.logsdb.enabled` setting was always `false` by default in
stateful Kibana. With the new changes, it is `true` by default if the
`logsdb.prior_logs_usage` setting is `false` (which is the case for new
test clusters, hence the test failure), and `true` otherwise. Therefore,
we need to update the tests so that we test both cases.

Flaky test runner:
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7821

(cherry picked from commit 96e3d55)
@kibanamachine kibanamachine reopened this Feb 19, 2025
@kibanamachine
Copy link
Contributor Author

New failure: kibana-es-forward-compatibility-testing-9-dot-0 - 8.x

@kibanamachine
Copy link
Contributor Author

New failure: kibana-es-forward-compatibility-testing-9-dot-0 - 8.x

@kibanamachine
Copy link
Contributor Author

New failure: kibana-es-forward-compatibility-testing-9-dot-0 - 8.x

@kibanamachine
Copy link
Contributor Author

New failure: kibana-es-forward-compatibility-testing-9-dot-0 - 8.x

@kibanamachine
Copy link
Contributor Author

New failure: kibana-es-forward-compatibility-testing-9-dot-0 - 8.x

@kibanamachine
Copy link
Contributor Author

New failure: kibana-es-forward-compatibility-testing-9-dot-0 - 8.x

@kibanamachine
Copy link
Contributor Author

New failure: kibana-es-forward-compatibility-testing-9-dot-0 - 8.x

@kibanamachine
Copy link
Contributor Author

New failure: kibana-es-forward-compatibility-testing-9-dot-0 - 8.x

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ElenaStoeva ElenaStoeva

Labels
failed-es-promotion failed-test A test failure on a tracked branch, potentially flaky-test Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Data Streams] Unskip API integration tests ElenaStoeva/kibana
4 participants
@mistic @elasticmachine @kibanamachine @ElenaStoeva