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

[BUG] Migration check on same version throws error while scaling Dashboards. #1303

Open
mihirsoni opened this issue Mar 1, 2022 · 1 comment
Labels
bug Something isn't working needs more info Requires more information from poster

Comments

@mihirsoni
Copy link
Contributor

Describe the bug

Since OpenSource Dashboards has been forked and changed it's version to 1.0 the current migration logic checks the version and halt the startup.

To Reproduce
Steps to reproduce the behavior:

  • Start Dashboards with FGAC domain
  • Create multiple tenants
  • Add another node / container to existing Dashboards fleet (Blue / Green) .
  • Now the new container will complain that index needs to be migrated.

Expected behavior
It should not throw this error

OpenSearch Version
1.0

Dashboards Version
1.0

Plugins

All plugins (FGAC included)

Additional context

Here is sample log error

{"type":"log","@timestamp":"2022-03-01T20:23:12Z","tags":["error","plugins","securityDashboards"],"pid":9630,"message":"Error: Index .kibana_-1085563064_some_random_name_1 belongs to a version of OpenSearch Dashboards that cannot be automatically migrated. Reset it or use the X-Pack upgrade assistant.\n    at assertIsSupportedIndex at Object.fetchInfo (rc/core/server/saved_objects/migrations/core/opensearch_index.js:82:10)\n    at process._tickCallback (internal/process/next_tick.js:68:7)"}
@mihirsoni mihirsoni added bug Something isn't working untriaged labels Mar 1, 2022
kavilla added a commit to kavilla/OpenSearch-Dashboards-1 that referenced this issue Mar 3, 2022
When an index migration failed it would show a message
that is no longer valid. Removing the reference.

Related issue:
opensearch-project#1303

Signed-off-by: Kawika Avilla <kavilla414@gmail.com>
@ahopp
Copy link
Contributor

ahopp commented Mar 8, 2022

@mihirsoni Following up on this. Can you verify the cluster was health at the the the node was add?

Additionally, can you verify the mappings were correct and healthy? Our assumption is yes, but wanted to make sure.

@ahopp ahopp added needs more info Requires more information from poster and removed untriaged labels Mar 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs more info Requires more information from poster
Projects
None yet
Development

No branches or pull requests

2 participants