Trove Integration

unstack.sh does not terminate trove-conductor properly

Bug #1322730 reported by Anna Shen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Trove Integration
Triaged
Medium
Unassigned
Trove Integration juno-3

Bug Description

As shown below, leftover trove-conductor processes after running ./unstack.sh

=====

ubuntu@devstack-neutron8:~/devstack$ ps aux | grep trove-conductor
ubuntu 19015 0.6 0.5 190964 41668 ? S 18:54 0:21 /usr/bin/python /usr/local/bin/trove-conductor --config-file=/etc/trove/trove-conductor.conf --debug
ubuntu 22100 0.0 0.5 208184 44160 ? S 19:44 0:00 /usr/bin/python /usr/local/bin/trove-conductor --config-file=/etc/trove/trove-conductor.conf --debug
ubuntu 23056 0.0 0.0 8112 932 pts/0 S+ 19:46 0:00 grep --color=auto trove-conductor

Nikhil Manchanda (slicknik)
Changed in trove-integration:
importance: Undecided → Medium
status: New → Triaged
milestone: none → juno-2
Nikhil Manchanda (slicknik)
Changed in trove-integration:
milestone: juno-2 → juno-3
Revision history for this message
vigneshvar (vigneshvar-a-s) wrote :

I tried to repeat the issue, but i dont find it occuring. Any specific scenarios ?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.