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.

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

Failing ES Promotion: FTR Configs #62 / Upgrade Assistant Deprecation pages renders the Elasticsearch upgrade readiness deprecations #160833

Closed
mistic opened this issue Jun 29, 2023 · 6 comments · Fixed by #163438
Assignees
Labels
failed-es-promotion Feature:Upgrade Assistant Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@mistic
Copy link
Member

mistic commented Jun 29, 2023

Chrome X-Pack UI Functional Tests
x-pack/test/functional/apps/upgrade_assistant/deprecation_pages.ts

Upgrade Assistant Deprecation pages renders the Elasticsearch upgrade readiness deprecations

This failure is preventing the promotion of the current Elasticsearch snapshot.

For more information on the Elasticsearch snapshot process including how to reproduce using the unverified ES build please read the failed promotion annotation. Other important information can be found at:

Error: expected [ 'Disk usage exceeds low watermark' ] to contain 'The cluster has too many shards to be able to upgrade'
    at Assertion.assert (expect.js:100:11)
    at Assertion.contain (expect.js:447:10)
    at Context.<anonymous> (deprecation_pages.ts:115:38)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at Object.apply (wrap_function.js:73:16)
@mistic mistic added blocker Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc skipped-test failed-es-promotion v8.10.0 labels Jun 29, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-core (Team:Core)

@mistic
Copy link
Member Author

mistic commented Jun 29, 2023

Skipped.

main: 277a208

@pgayvallet
Copy link
Contributor

cc @Bamieh

@sophiec20
Copy link
Contributor

This test failure appears to be directly related to a newer version of Elasticsearch. This test was skipped in order to unblock the Elasticsearch snapshot promotion.

So that we can be ready to release from main, we ask for failed-es-promotion issues to be treated with greater urgency. Please acknowledge and triage this issue.

@rudolf rudolf added Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more Feature:Upgrade Assistant labels Aug 1, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/platform-deployment-management (Team:Deployment Management)

@rudolf rudolf removed the Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more label Aug 1, 2023
@Bamieh
Copy link
Member

Bamieh commented Aug 3, 2023

@sophiec20 acknowledged 👍 debugging and working on a fix now

Bamieh added a commit that referenced this issue Aug 8, 2023
## Summary
Create a new functional config file that sets up elasticsearch configs
to have a low disk threshold and a low number of shards per node to test
for health checks and deprecations.

Previously this test failed because it seems that ES takes some time to
calculate the health checks hence the indicator critical issues are not
showing during the testing period (now we don't have flakiness since we
started the server with the indicators already in place) it also means
less `before` and `after` work inside the test cases.

Closes #160833

---------

Co-authored-by: kibanamachine <[email protected]>
bryce-b pushed a commit to bryce-b/kibana that referenced this issue Aug 9, 2023
)

## Summary
Create a new functional config file that sets up elasticsearch configs
to have a low disk threshold and a low number of shards per node to test
for health checks and deprecations.

Previously this test failed because it seems that ES takes some time to
calculate the health checks hence the indicator critical issues are not
showing during the testing period (now we don't have flakiness since we
started the server with the indicators already in place) it also means
less `before` and `after` work inside the test cases.

Closes elastic#160833

---------

Co-authored-by: kibanamachine <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
failed-es-promotion Feature:Upgrade Assistant Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants