puppet-elasticsearch: Plugins installed with wrong ownership
I’ve just upgraded from 0.9.9 to 0.10.2 of this plugin, and it looks like https://github.com/elastic/puppet-elasticsearch/issues/107 has returned. Plugins are installed/owned by root, which means they can’t be read by the elasticsearch user when starting ES. I was able to get around this by running the following manually:
chown -R elasticsearch.elasticsearch /usr/share/elasticsearch/plugins/
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 22 (15 by maintainers)
Without casting blame here, this is definitely something that arises out of end-user changes to the system, and the module functions entirely correctly out-of-the box by default. This is only an issue when folks make some change that skews the umask that plugins are installed with.
The super conservative response here would be “if you’re changing the umask, it’s your responsibility to ensure the fallout doesn’t break anything”, but practically, the module does some shifty things to figure out what the plugin directory name is, so it’s far easier to control this directly in the module where we can reliably determine the plugin directory’s name.
The changeset in #685 makes that happen by ensuring the relevant plugin dir is (basically)
chmod -R o+Xr. The change should be in the next release.