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

cp-solr-xml fails when a local backup repository is configured with SolrCloud running as a custom user #519

Closed
a-nych opened this issue Jan 23, 2023 · 0 comments · Fixed by #520
Labels
bug Something isn't working custom kube options Adding options related to customizing parts of the default Kubernetes resources.
Milestone

Comments

@a-nych
Copy link
Contributor

a-nych commented Jan 23, 2023

Steps to reproduce:

  1. Run SolrCloud nodes with podOptions.podSecurityContext.runAsUser and podOptions.podSecurityContext.fsGroup set to anything other than 8983 (default SolrCloud user)
  2. Configure a local backupRepository using persistentVolumeClaim

cp-solr-xml will then run chmod -r 8983:8983 <backup_storage_path> despite us running Solr with different users. At some point when files are created in the backup repository by SolrCloud, the chmod command will fail due to missing permissions and SolrCloud won't boot.

@HoustonPutman HoustonPutman added this to the v0.7.0 milestone Apr 24, 2023
@HoustonPutman HoustonPutman added bug Something isn't working custom kube options Adding options related to customizing parts of the default Kubernetes resources. labels Apr 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working custom kube options Adding options related to customizing parts of the default Kubernetes resources.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants