b257b2a676
In case of trove-api service config file modification (trove.conf file), trove-conductor and trove-taskmanager are restarted too, but they should not. trove-conductor startup command: https://github.com/openstack/kolla-ansible/blob/master/ansible/roles/trove/templates/trove-conductor.json.j2#L2 => trove.conf is not used trove-taskmanager startup command: https://github.com/openstack/kolla-ansible/blob/master/ansible/roles/trove/templates/trove-taskmanager.json.j2#L2 => trove.conf is not used Change-Id: Ic4703a571cec5bf8b3f91cfcb9da1a23e2bb300b Closes-Bug: #1677531 |
||
---|---|---|
.. | ||
action_plugins | ||
group_vars | ||
inventory | ||
library | ||
roles | ||
bifrost.yml | ||
certificates.yml | ||
destroy.yml | ||
kolla-host.yml | ||
mariadb_recovery.yml | ||
post-deploy.yml | ||
site.yml | ||
stop.yml |