Open hnc-lcy9104 opened 4 days ago
Hi @hnc-lcy9104
I was able to reproduce the issue with that particular plugin, but I was able to install other plugins (e.g. analysis-icu
). It looks like the issue you're facing is related to filesystem permissions, under investigation.
Also, according to this link, it says, "The Bitnami OpenSearch Docker image comes with the S3 Repository plugin installed by default," so shouldn’t the repository-s3 plugin already be installed?
This looks like a copy-paste error given OpenSearch's README was based on ElasticSearch one. As you can see in the logs below, if you try to install that plugin using ElasticSearch you find a warning saying it's already packaged:
elasticsearch 11:15:18.74 DEBUG ==> Installing plugin: repository-s3
-> Installing repository-s3
[repository-s3] is no longer a plugin but instead a module packaged with this distribution of Elasticsearch
-> Please restart Elasticsearch to activate any plugins installed
I'll send a PR to amend it.
Name and Version
bitnami/opensearch 1.2.10
What architecture are you using?
None
What steps will reproduce the bug?
Are you using any custom parameters or values?
What is the expected behavior?
Install plugins.
What do you see instead?
I added plugins: repository-s3 to the values.yaml that was working fine, but a new pod is not being created. After removing plugins: repository-s3 from values.yaml and running opensearch-plugin install repository-s3 by executing into the pod with exec bash, I got the following result: opensearch-plugin install repository-s3
Also, according to this link, it says, "The Bitnami OpenSearch Docker image comes with the S3 Repository plugin installed by default," so shouldn’t the repository-s3 plugin already be installed?
However, when I run the opensearch-plugin list command, it is not listed.
Additional information
No response