-
Notifications
You must be signed in to change notification settings - Fork 71
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 delete reporting created index .opendistro-reports-definitions #627
Comments
Found a solution for the issue:
If you use the certificate to authenticate, you will be able to delete the index. What I do not understand though, is the difference of using the cert versus the basic auth user. Maybe someone could explain the difference to me. It would also be helpful if these plugins will create shards with at least one replica by default. |
I'll move this to opensearch-devops, hopefully someone will know! |
Actually looks like this is coming from reporting ... |
using certificates will give you permission as superadmin, who will be able to remove system indices, and reporting indices are system indices somewhat related: maybe we can give regular admin permission to manage them #955 i'll close this issue for now since there's a workaround, you can read more about super admin here https://opensearch.org/docs/latest/security/access-control/users-roles/#super-admin-users |
Describe the bug
Unable to delete reporting created index.
To Reproduce
Try to delete/change the index
Expected behavior
Index is deleted
Plugins
opensearch-alerting 1.3.6.0
opensearch-anomaly-detection 1.3.6.0
opensearch-asynchronous-search 1.3.6.0
opensearch-cross-cluster-replication 1.3.6.0
opensearch-index-management 1.3.6.0
opensearch-job-scheduler 1.3.6.0
opensearch-knn 1.3.6.0
opensearch-ml 1.3.6.0
opensearch-observability 1.3.6.0
opensearch-performance-analyzer 1.3.6.0
opensearch-reports-scheduler 1.3.6.0
opensearch-security 1.3.6.0
opensearch-sql 1.3.6.0
prometheus-exporter 1.3.6.0
Screenshots
Host/Environment (please complete the following information):
K8s using the opster operator
https://github.com/Opster/opensearch-k8s-operator
Additional context
The reason why I want to delete it, is that there are no replica's of this shard and it caused the cluster to be red.
The text was updated successfully, but these errors were encountered: