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: Kibana shows the wrong screen (index pattern creation) even if there are index patterns in the space #45748

Closed
friol opened this issue Sep 14, 2019 · 3 comments
Labels
bug Fixes for quality problems that affect the customer experience

Comments

@friol
Copy link
Contributor

friol commented Sep 14, 2019

Kibana version: 8.0.0

Elasticsearch version: 8.0.0-SNAPSHOT

Server OS version: Windows 10

Browser version: Chrome 76

Browser OS version: Windows 10

Original install method (e.g. download page, yum, from source, etc.): Started Kibana from source downloading the latest master

Describe the bug:
Index patterns exist, but "Discover" shows the "In order to visualize and explore data in Kibana, you'll need to create an index pattern to retrieve data from Elasticsearch." page and forces me to create a new index pattern.

Steps to reproduce:

  1. Start Kibana, create a new space
  2. Import saved objects (an index pattern and a saved search) from the attached file into that space
  3. Go to discover

Expected behavior:
Discover shows the imported index pattern (the only one in that space)

Screenshots (if relevant):
indexPatternCreation

Errors in browser console (if relevant):
None

Provide logs and/or server output (if relevant):
There are no logsfor this action.

Any additional context:
export.zip

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app-arch

@legrego
Copy link
Member

legrego commented Sep 18, 2019

Note: likely unrelated to Spaces, but rather the index pattern cache. Doing a hard browser refresh (hopefully) loads the index pattern correctly.

@Dosant Dosant added bug Fixes for quality problems that affect the customer experience and removed triage_needed labels Dec 10, 2020
@Dosant
Copy link
Contributor

Dosant commented Dec 10, 2020

this should be fixed by #63329

@Dosant Dosant closed this as completed Dec 10, 2020
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
Projects
None yet
Development

No branches or pull requests

4 participants