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

Default index pattern not being preserved across upgrades #22541

Closed
jayjanssen opened this issue Aug 30, 2018 · 3 comments · Fixed by #24108
Closed

Default index pattern not being preserved across upgrades #22541

jayjanssen opened this issue Aug 30, 2018 · 3 comments · Fixed by #24108
Assignees
Labels
enhancement New value added to drive a business result good first issue low hanging fruit

Comments

@jayjanssen
Copy link

Kibana version:

Kibana 6.X (most recently on 6.4.0)

Elasticsearch version:

6.X

Server OS version:

Official Docker image

Original install method (e.g. download page, yum, from source, etc.):

Docker

Describe the bug:

Every time I upgrade Kibana (which runs in Docker for me), I have to re-set the Default index. All my other kibana settings (index pattern definitions, visualizations, dashboards, etc.) are preserved correctly. I run several kibana instances on the same cluster, so I set KIBANA_INDEX (differently) for each instance

KIBANA_INDEX=.kibana-1

Steps to reproduce:

  1. Assume ES 6.4.0 is running with at least two indexes and can be reached at http://host.docker.internal:9200
  2. docker run --name=kibana-test -p 1234:5601 -e ELASTICSEARCH_URL=http://host.docker.internal:9200 -e KIBANA_INDEX=.kibana-1234 docker.elastic.co/kibana/kibana:6.3.2
  3. Go to http://127.0.0.1:1234, create two index patterns and set one as default index
  4. docker stop kibana-test && docker rm kibana-test
  5. docker run --name=kibana-test -p 1234:5601 -e ELASTICSEARCH_URL=http://host.docker.internal:9200 -e KIBANA_INDEX=.kibana-1234 docker.elastic.co/kibana/kibana:6.4.0
  6. Revisit http://127.0.0.1:1234 and click 'Discover' -- you have to set the default index again.

Expected behavior:

I expect my default index setting to be stored like everything else, but it doesn't seem to be getting preserved.

Screenshots (if relevant):
Result of step 6:
screen shot 2018-08-30 at 9 18 26 am

Any additional context:
This is frustrating because I have several different Kibana instances that I upgrade all at once and I have to visit each of them to re-set the default index on every upgrade.

@bhavyarm bhavyarm added :Management triage_needed enhancement New value added to drive a business result labels Aug 30, 2018
@bmcconaghy bmcconaghy added good first issue low hanging fruit and removed triage_needed labels Sep 4, 2018
@bmcconaghy bmcconaghy assigned bmcconaghy and unassigned cjcenizal Sep 18, 2018
@evanfreed
Copy link

Adding a +1, I've seen a similar behavior when:

  1. Exporting dashboards, visualizations, searches and index patterns through the Kibana Rest API to disk
  2. Deleting all existing dashboards, visualizations, searches, and index patterns
  3. Submitting all objects back through the API
  4. Reopening Kibana and selecting dashboards fails due to not setting default index pattern.

@bmcconaghy
Copy link
Contributor

bmcconaghy commented Sep 20, 2018

@evanfreed so I have fixed the original issue related to migrations. I do not think your issue is related as I originally thought it might be, so would you mind submitting your issue as a new one and pinging me on it?

@spalger
Copy link
Contributor

spalger commented Oct 16, 2018

Reverted #23377

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result good first issue low hanging fruit
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants