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] Unable to create index pattern using all_access role #945

Open
oleksandrfatikov opened this issue Nov 29, 2023 · 1 comment
Open
Labels
bug Something isn't working

Comments

@oleksandrfatikov
Copy link

Describe the bug
I’m trying to create an index pattern on newly set up opensearch in k8s. Once I create it and get back to ‘Discover’ tab, there are no index patterns and opensearch suggest creating new one.

To Reproduce
Steps to reproduce the behavior:

  1. Install opensearch and dashboards in k8s using helm charts;
  2. Install fluent-bit to deliver logs to opensearch;
  3. Login under ‘admin’ user with ‘all_access’ role;
  4. Go to ‘Discover’ on WI and create a new pattern;
  5. Pattern is created (screenshot attached);
  6. Go back to ‘Discover’ and there are no index patterns;

Expected behavior
The index pattern is created and I can browse logs from 'Discover' tab.

Screenshots
45e9ab45195d0f5d1425a3ad8f3f16a6db0fae33

Host/Environment (please complete the following information):
Environment: k8s v1.27.2
Opensearch/dashboards version: 2.11.0
Opensearch chart version: 2.16.1
Dashboards chart version: 2.14.0

Additional context

  • I created clusters previously and deleted them along with the disk volumes, so it should be a clean install, but may be this is somehow connected, because I can’t see other reason for such behavior.
  • Also if I go to ‘Saved Objects’ on 'Index patterns' page, I get the following error in the browser console:
    "message": "all shards failed: search_phase_execution_exception: [illegal_argument_exception] Reason: Text fields are not optimised for operations that require per-document field data like aggregations and sorting, so these operations are disabled by default. Please use a keyword field instead. Alternatively, set fielddata=true on [type] in order to load field data by uninverting the inverted index. Note that this can use significant memory."
@oleksandrfatikov oleksandrfatikov added bug Something isn't working untriaged labels Nov 29, 2023
@dblock dblock transferred this issue from opensearch-project/OpenSearch Nov 29, 2023
@dblock
Copy link
Member

dblock commented Jun 17, 2024

Looks like a bug. Thanks for reporting it. Catch All Triage - 1 2 3 4 5

@dblock dblock removed the untriaged label Jun 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants