Browse code
make stop_neutron actually stop neutron
stop_neutron doesn't actually stop neutron. The only reason grenade
neutron job was working was due to some blanket kills that never got
removed. As you can see it doesn't even actually attempt to stop most
of the services in question. Apparently it's doing some edge case
cleaning because neutron services don't actually shut down their child
processes correctly.
This actually makes stop_neutron do a thing.
Change-Id: I9138a8370be06e6c9d2dacbec1b0ffd4928e603d
Sean Dague authored on 2015/04/11 19:34:09Showing 1 changed files
| ... | ... |
@@ -685,6 +685,18 @@ function start_neutron_agents {
|
| 685 | 685 |
|
| 686 | 686 |
# stop_neutron() - Stop running processes (non-screen) |
| 687 | 687 |
function stop_neutron {
|
| 688 |
+ stop_process q-svc |
|
| 689 |
+ stop_process q-agent |
|
| 690 |
+ stop_process q-dhcp |
|
| 691 |
+ stop_process q-lbaas |
|
| 692 |
+ stop_process q-fwaas |
|
| 693 |
+ stop_process q-vpn |
|
| 694 |
+ stop_process q-l3 |
|
| 695 |
+ stop_process q-metering |
|
| 696 |
+ |
|
| 697 |
+ # BUG: this is all legacy gorp by previous attempts that don't |
|
| 698 |
+ # really understand how devstack works. It can probably mostly be |
|
| 699 |
+ # removed. |
|
| 688 | 700 |
if is_service_enabled q-dhcp; then |
| 689 | 701 |
pid=$(ps aux | awk '/[d]nsmasq.+interface=(tap|ns-)/ { print $2 }')
|
| 690 | 702 |
[ ! -z "$pid" ] && sudo kill -9 $pid |