← Back to team overview

group.of.nepali.translators team mailing list archive

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

 

This bug was fixed in the package openstack-trove - 1:6.0.0~b2-0ubuntu1

---------------
openstack-trove (1:6.0.0~b2-0ubuntu1) yakkety; urgency=medium

  [ Corey Bryant ]
  * New upstream milestone for OpenStack Newton.
  * d/control: Align (build-)depends with upstream.
  * d/rules: Run unit tests with ostestr.
  * d/p/patch-default-config-file.patch: Rebased.

  [ James Page ]
  * New upstream version.
  * d/p/fix-base-unit-test-class.patch: Drop, no longer required.
  * d/*.init.in: Use correct configuration file for each of the trove
    daemons (LP: #1516471).
  * d/p/*: Refresh.

  [ David Della Vecchia ]
  * d/p/skip-failing-tests.patch: Rebased.

 -- Corey Bryant <corey.bryant@xxxxxxxxxxxxx>  Mon, 11 Jul 2016 16:06:09
-0400

** Changed in: openstack-trove (Ubuntu Yakkety)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
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:
  Triaged
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