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.