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

[Upgrade Assistant] After reindexing a data stream, "Close" button disappears #210257

Open
tsullivan opened this issue Feb 7, 2025 · 3 comments
Labels
bug Fixes for quality problems that affect the customer experience Feature:Upgrade Assistant Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more

Comments

@tsullivan
Copy link
Member

Description

This issue describes user experience problems of inconsistency between different types of reindexing, and a source of user confusion caused by a self-updating UI.

Steps:

  • In 7.17.28-SNAPSHOT, run Elasticsearch and Kibana and add some custom data to in index
  • Upgrade to 8.0.0
  • Upgrade to 8.18.0-SNAPSHOT
  • Go to "Stack Management > Upgrade Assistant"
    • Navigate to "Elasticsearch deprecation issues"
    • Select an issue for "Old index with a compatibility version < 8.0"
      • Follow the steps through reindexing the old index
      • Note how during the process and at the end of the process, the side panel does have a "Close" button at the bottom.
      • Note how at the end of the process, the reindexing details are still shown
      • Close the side panel
    • Select an issue for "Old data stream with a compatibility version < 8.0"
      • Follow the steps through reindexing the data stream
      • Note how during the process, the side panel does have a "Close" button at the bottom, but does not at the end of the process.
      • Note how at the end of the process, the contents of the panel self-update. The reindexing details are replaced and are no longer shown

Question:

  • Should there even be a "Close" button during a reindexing process?
reindexing-issues.mov
@tsullivan tsullivan added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Feature:Upgrade Assistant labels Feb 7, 2025
@elasticmachine
Copy link
Contributor

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

@tsullivan tsullivan added the Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more label Feb 7, 2025
@elasticmachine
Copy link
Contributor

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

@tsullivan tsullivan added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc and removed Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc labels Feb 7, 2025
@TinaHeiligers TinaHeiligers added the bug Fixes for quality problems that affect the customer experience label Feb 11, 2025
@TinaHeiligers
Copy link
Contributor

Todo: triage behavior of closing the flyout on reindexing status. Ideally, selecting the "close" button shouldn't stop the reindexing process. If it does, ensure it's disabled until reindexing is complete.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Upgrade Assistant Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more
Projects
None yet
Development

No branches or pull requests

3 participants