For each fullstack test I execute, I get a new neutron-server instance hanging there:
6717 pts/1 S 0:00 /opt/stack/neutron/.tox/dsvm-fullstack/bin/python /opt/stack/neutron/.tox/dsvm-fullstack/bin/neutron-server --log-dir /tmp/dsvm-fullstack-logs/TestConnectivitySameNetwork.test_connectivity --log-file neutron-server--2015-09-10--17-01-31-376365.log --config-file /tmp/tmppafpKE/tmpgiLm_2/neutron.conf --config-file /tmp/tmppafpKE/tmpgiLm_2/ml2_conf.ini
6718 pts/1 S 0:01 /opt/stack/neutron/.tox/dsvm-fullstack/bin/python /opt/stack/neutron/.tox/dsvm-fullstack/bin/neutron-server --log-dir /tmp/dsvm-fullstack-logs/TestConnectivitySameNetwork.test_connectivity --log-file neutron-server--2015-09-10--17-01-31-376365.log --config-file /tmp/tmppafpKE/tmpgiLm_2/neutron.conf --config-file /tmp/tmppafpKE/tmpgiLm_2/ml2_conf.ini
6719 pts/1 S 0:00 /opt/stack/neutron/.tox/dsvm-fullstack/bin/python /opt/stack/neutron/.tox/dsvm-fullstack/bin/neutron-server --log-dir /tmp/dsvm-fullstack-logs/TestConnectivitySameNetwork.test_connectivity --log-file neutron-server--2015-09-10--17-01-31-376365.log --config-file /tmp/tmppafpKE/tmpgiLm_2/neutron.conf --config-file /tmp/tmppafpKE/tmpgiLm_2/ml2_conf.ini
I believe ProcessFixture does not behave with neutron-server, probably because of workers.
Yes, ps -ef shows that all processes are owned by init process, meaning their parent died.