systemd init scripts not setting correct conf file
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-trove (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Wily |
Triaged
|
High
|
Unassigned | ||
Xenial |
Fix Committed
|
High
|
Unassigned | ||
Yakkety |
Fix Released
|
High
|
Unassigned |
Bug Description
In january the trove install packages were changed to use systemd in this commit:
http://
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-
trove 16510 1 0 Nov13 ? 00:09:13 /usr/bin/python /usr/bin/
trove 16574 16464 0 Nov13 ? 00:00:00 /usr/bin/python /usr/bin/trove-api --config-
trove 16575 16464 0 Nov13 ? 00:00:00 /usr/bin/python /usr/bin/trove-api --config-
trove 16576 16510 0 Nov13 ? 00:00:02 /usr/bin/python /usr/bin/
trove 16579 16510 0 Nov13 ? 00:00:02 /usr/bin/python /usr/bin/
trove 28190 1 0 14:32 ? 00:00:00 /usr/bin/python /usr/bin/
You will notice that all services are using trove.conf when they should be using trove-conductor
The *.init.in files need updating to include settings like: CONFIG_
Changed in openstack-trove (Ubuntu): | |
status: | Confirmed → Triaged |
importance: | Undecided → High |
Changed in openstack-trove (Ubuntu Yakkety): | |
status: | Triaged → Fix Committed |
Changed in openstack-trove (Ubuntu Xenial): | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in openstack-trove (Ubuntu Wily): | |
status: | New → Triaged |
importance: | Undecided → High |
Status changed to 'Confirmed' because the bug affects multiple users.