yahoo-eng-team team mailing list archive

[Ihar Hrachyshka <1494363@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1494363

Title:
  fullstack tests leave neutron-server running

Status in neutron:
  New

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1494363/+subscriptions