[Bug 1516471] Re: systemd init scripts not setting correct conf file

[Pete MacKinnon]

Actually oslo_config should compute and search for the appropriate
config files for you. For example, in the case of trove-taskmanager, it
will take the program name ("trove-taskmanager"), prepend it with a dir
based on the project name ("/etc/trove"), and append the ".conf"
extension.

['/usr/share/trove/trove-dist.conf',
 None,
 '/etc/trove/trove.conf',
 '/etc/trove/trove-taskmanager.conf']

Thus, it shouldn't be necessary to specify the config file at all given
a standard install. YMMV

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to openstack-trove in Ubuntu.
https://bugs.launchpad.net/bugs/1516471

Title:
  systemd init scripts not setting correct conf file

Status in openstack-trove package in Ubuntu:
  Fix Committed
Status in openstack-trove source package in Wily:
  Triaged
Status in openstack-trove source package in Xenial:
  Triaged
Status in openstack-trove source package in Yakkety:
  Fix Committed

Bug description:
  In january the trove install packages were changed to use systemd in this commit:
  http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/wily/openstack-trove/wily/revision/21
  This caused all services to startup using the same configuration file. 

  trove    16464     1  0 Nov13 ?        00:09:24 /usr/bin/python /usr/bin/trove-api --config-file=/etc/trove/trove.conf --log-file=/var/log/trove/trove-api.log
  trove    16510     1  0 Nov13 ?        00:09:13 /usr/bin/python /usr/bin/trove-conductor --config-file=/etc/trove/trove.conf --log-file=/var/log/trove/trove-conductor.log
  trove    16574 16464  0 Nov13 ?        00:00:00 /usr/bin/python /usr/bin/trove-api --config-file=/etc/trove/trove.conf --log-file=/var/log/trove/trove-api.log
  trove    16575 16464  0 Nov13 ?        00:00:00 /usr/bin/python /usr/bin/trove-api --config-file=/etc/trove/trove.conf --log-file=/var/log/trove/trove-api.log
  trove    16576 16510  0 Nov13 ?        00:00:02 /usr/bin/python /usr/bin/trove-conductor --config-file=/etc/trove/trove.conf --log-file=/var/log/trove/trove-conductor.log
  trove    16579 16510  0 Nov13 ?        00:00:02 /usr/bin/python /usr/bin/trove-conductor --config-file=/etc/trove/trove.conf --log-file=/var/log/trove/trove-conductor.log
  trove    28190     1  0 14:32 ?        00:00:00 /usr/bin/python /usr/bin/trove-taskmanager --config-file=/etc/trove/trove.conf --log-file=/var/log/trove/trove-taskmanager.log

  You will notice that all services are using trove.conf when they
  should be using trove-conductor.conf, trove-taskmanager.conf etc

  The *.init.in files need updating to include settings like:
  CONFIG_FILE=/etc/${PROJECT_NAME}/trove-taskmanager.conf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openstack-trove/+bug/1516471/+subscriptions