FS#64106 - [elasticsearch] Wrong 'EnvironmentFile' in systemd unit files

Attached to Project: Community Packages
Opened by David Wheeler (dwheeler) - Saturday, 12 October 2019, 13:55 GMT
Last edited by Massimiliano Torromeo (mtorromeo) - Tuesday, 15 October 2019, 13:59 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Massimiliano Torromeo (mtorromeo)
Levente Polyak (anthraxx)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
EnvironmentFile was changed from /etc/default/elasticsearch to /etc/sysconfig/elasticsearch in commit b7aaa8c5b6185b0519be61946f8614b7cabaa125.
https://git.archlinux.org/svntogit/community.git/commit/trunk?h=packages/elasticsearch&id=b7aaa8c5b6185b0519be61946f8614b7cabaa125

This is causing the environment file to not be read at all. Archlinux uses /etc/default, and (at least on my system) /etc/sysconfig doesn't even exist. The package also still uses /etc/default for this file in the backup array. Testing shows that changing the unit files back to /etc/default fixes the issue.


Steps to reproduce:
Add a test variable to /etc/default/elasticsearch. Start elasticsearch. Verify the test variable has not been set in elasticsearch's environment.
This task depends upon

Closed by  Massimiliano Torromeo (mtorromeo)
Tuesday, 15 October 2019, 13:59 GMT
Reason for closing:  Fixed
Additional comments about closing:  elasticsearch 7.4.0-2
Comment by David Wheeler (dwheeler) - Saturday, 12 October 2019, 14:02 GMT
Package version: 7.4.0-1

Loading...