-
Notifications
You must be signed in to change notification settings - Fork 274
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
Unable to update index pattern #4112
Comments
@opensearch-project/admin could we route to security plugin? a first step is to add more doc to clearly let cx aware of the issue. |
@opensearch-project/admin Can this issue be routed to security plugin team to take a look? |
[Triage] @peternied Can you take a look at this issue and ask any questions that would help with a reproduction to determine if this is a bug or config related issue that documentation can alleviate? |
@rlevytskyi Thanks for opening this issue - as this behavior can be confusing. For your sysadmin accounts/clients make sure that no roles are applied that include DLS/FLS rules [1] - including roles that are included by network policies. We have been consider investing into Views, which could help facilitate better DLS/FLS rules organization [2] [3] that might avoid these scenarios. Thoughts on this would be greatly appreciated. |
Closing this out as there isn't a specific bug here. |
Describe the bug
At some point, our users started complaining they are unable to update their index patterns.
Even I as cluster_admin unable to update them, getting this at kibana log:
And this at coordinating node log:
To Reproduce
Steps to reproduce the behavior:
"dls": "{ \"bool\": { \"must_not\": [ { \"match_phrase\": { \"host\": \"v000.company.com\" } } ] } }"
and see index pattern can now be updated.
Expected behavior
The initial reason is that roles got overlapped when one has empty DSL.
OpenSearch Version
OpenDistro 1.0 through OpenSearch 2.12
Dashboards Version
OpenDistro 1.0 through OpenSearch 2.12
Plugins
Screenshots
Not applicable, see logs.
Host/Environment (please complete the following information):
Additional context
Will be added upon request.
The text was updated successfully, but these errors were encountered: