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

[Brian Murray]

Hello Andrew, or anyone else affected,

Accepted openstack-trove into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/openstack-
trove/1:5.0.1-0ubuntu1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: openstack-trove (Ubuntu Xenial)
       Status: Triaged => Fix Committed

** Tags added: verification-needed

-- 
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 Released
Status in openstack-trove source package in Wily:
  Triaged
Status in openstack-trove source package in Xenial:
  Fix Committed
Status in openstack-trove source package in Yakkety:
  Fix Released

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