unstack.sh will not kill the n-cpu spawned in Ubuntu12.04

[yalei wang]

n-cpu is spawned by this command now if you use libvirtd:

sg libvirtd '/usr/local/bin/nova-compute --config-file /etc/nova/nova.conf'

it runs in libvirtd group, and there will be two processes spawned for n-cpu.

$ ps aux |grep compu
root 28490 0.0 0.0 15028 1024 pts/20 S+ 14:18 0:00 sg libvirtd /usr/local/bin/nova-compute --config-file /etc/nova/nova.conf
neutron 28491 1.1 2.5 1851612 101432 pts/20 Sl+ 14:18 0:06 /usr/bin/python /usr/local/bin/nova-compute --config-file /etc/nova/nova.conf

and when u call unstack.sh, the stop_process in functions-common will be called . BUT

pkill -g 28490 will only kill 28490, and process 28491 will be left.
some error will emit, because that process will still occupy the source , like database(you can drop database if you use postgresql).

I use the ubuntu 12.04 and the pkill 's version is:

$ pkill -V
pkill (procps version 3.2.8)

and kill 28491 twice, is can be killed immediately.

[yalei wang (yalei-wang)]

the TERM signal will be handled in nova in function _wait_for_exit_or_signal in file nova/openstack/common/service.py

and will never return currently.

[Sean Dague (sdague)]

This devstack bug was last updated over 180 days ago, as devstack
is a fast moving project and we'd like to get the tracker down to
currently actionable bugs, this is getting marked as Invalid. If the
issue still exists, please feel free to reopen it.