opensearch-project / helm-charts

:wheel_of_dharma: A community repository for Helm Charts of OpenSearch Project.
https://opensearch.org/docs/latest/opensearch/install/helm/
Apache License 2.0
170 stars 228 forks source link

Opensearch Cannot apply default config (this is maybe not an error!) #398

Closed rakeshreddyrg09 closed 1 year ago

rakeshreddyrg09 commented 1 year ago

Describe the bug Opensearch Cannot apply default config (this is maybe not an error!) To Reproduce Steps to reproduce the behavior:

  1. downloaded the charts -- from here -->https://github.com/opensearch-project/helm-charts/tree/main/charts
  2. Applied os and os-dashboard charts getting below errors
  3. Opensearch master pod error image
  4. [o.o.s.c.ConfigurationLoaderSecurity7] [opensearch-cluster-master-0] Exception while retrieving configuration for [INTERNALUSERS, ACTIONGROUPS, CONFIG, ROLES, ROL │ │ ESMAPPING, TENANTS, NODESDN, WHITELIST, ALLOWLIST, AUDIT] (index=.opendistro_security)

    Till this i have not applied the dashboard. Once i apply the dashboard i am getting one more error as below

image

  1. Dashboard error image

  2. here is my config file(default am using )

                 cluster.name: opensearch-cluster
                  # Bind to all interfaces because we don't know what IP address Docker will assign to us.
                  network.host: 0.0.0.0
                  # Setting network.host to a non-loopback address enables the annoying bootstrap checks. "Single-node" mode disables them again.
                  # Implicitly done if ".singleNode" is set to "true".
                  # discovery.type: single-node
                  # Start OpenSearch Security Demo Configuration
                  # WARNING: revise all the lines below before you go into production
                  plugins:
                    security:
                      ssl:
                        transport:
                          pemcert_filepath: esnode.pem
                          pemkey_filepath: esnode-key.pem
                          pemtrustedcas_filepath: root-ca.pem
                          enforce_hostname_verification: false
                        http:
                          enabled: true
                          pemcert_filepath: esnode.pem
                          pemkey_filepath: esnode-key.pem
                          pemtrustedcas_filepath: root-ca.pem
                      allow_unsafe_democertificates: true
                      allow_default_init_securityindex: true
                      authcz:
                        admin_dn:
                          - CN=kirk,OU=client,O=client,L=test,C=de
                      audit.type: internal_opensearch
                      enable_snapshot_restore_privilege: true
                      check_snapshot_restore_write_privileges: true
                      restapi:
                        roles_enabled: ["all_access", "security_rest_api_access"]
                      system_indices:
                        enabled: true
                        indices:
                          [
                            ".opendistro-alerting-config",
                            ".opendistro-alerting-alert*",
                            ".opendistro-anomaly-results*",
                            ".opendistro-anomaly-detector*",
                            ".opendistro-anomaly-checkpoints",
                            ".opendistro-anomaly-detection-state",
                            ".opendistro-reports-*",
                            ".opendistro-notifications-*",
                            ".opendistro-notebooks",
                            ".opendistro-asynchronous-search-response*",
                          ]
                  ######## End OpenSearch Security Demo Configuration ########

Can any one help me out, whats going wrong here. Thank you

prudhvigodithi commented 1 year ago

[Triage] Hey @rakeshreddyrg09 I assume you dint not change any setting in the values.yaml file, if so can you try with persistence.enableInitChown to false and run the chart again? Also how are the created persistent disks managed is it by any default cloud provider? @bbarani @DandyDeveloper @TheAlgo @peterzhuamazon

rakeshreddyrg09 commented 1 year ago

i got it resolved. i did a mistake in adding roles. thank you for the support.