faucet_mininet_test inconsistently fails outside docker container

I've been trying to get the faucet_mininet_test.py tests running outside a docker container and have all the software requirements installed. The problem is that some tests will fail intermittently and almost seem like it is due to race conditions. This occurs on:

Ubuntu 14.04 host > VMware WS 12 > Ubuntu 16.04 desktop guest
Ubuntu 14.04 host > VMware WS 12 > Ubuntu 16.04 server guest (fresh install for this test)
Ubuntu 14.04 host > Virtualbox 5 > Ubuntu 16.04 server guest (fresh install for this test)

However, the tests always seem to pass when run in the docker container (built locally from v1_0-265-g20168ee in the onfsd/faucet fork, as per README.docker.md). This works on:

Ubuntu 14.04 host > VMware WS 12 > Ubuntu 16.04 desktop guest > docker > reannz/faucet-test
Ubuntu 14.04 host > docker > reannz/faucet-test

Since this is working in docker on my Ubuntu 16.04 desktop guest, it should work outside the docker as well. The software requirements come from faucet_mininet_test.py itself.
However, when run outside the docker container, sometimes the tests pass, but most of the time it does not. I ran 10 tests in a row and recorded their results (only test and final exception provided in ticket description, attached full logs). Passes 3, 4, and 10 passed the tests completely, the rest failed in some manner. This would suggest that my checked out version of faucet can function properly on a VM.
I did notice in the docker, however, that Mininet complains that it can't make all the sysctl calls it needs:
================= Starting OVS ==================
 * /etc/openvswitch/conf.db does not exist
 * Creating empty database /etc/openvswitch/conf.db
 * Starting ovsdb-server
 * Configuring Open vSwitch system IDs
 * Starting ovs-vswitchd
 * Enabling remote OVSDB managers
=========== Running faucet unit tests ===========
test_tagged (faucet_mininet_test.FaucetMultipleDPTaggedTest) ... *** Error setting resource limits. Mininet's performance may be affected.
t4ds1h1 t4ds1h1-eth0.100:s14d-eth1
[...]

This may point to some weirdness where the test works under Docker conditions with reduced resources, but not directly on a VM, even the VM running the Docker instance. I've tried modifying the tests to run with user-mode OVS only, but got similar results. Since the Docker was run in privileged mode, I would guess that it has access to the kernel DP anyway.
I hope this information helps. I'm in the process of writing tutorials on setting up the latest dev version of Faucet after my last articles on covering the Ryu API and creating a Ryu controller application based in part on the table structure used in Faucet on Inside-OpenFlow.com.
In any case, I would rather write instructions to make this run without having to use Docker and I always try to have the reader run any tests supplied with manually installed software first to ensure software is installed properly before continuing to usage instructions. I plan on covering additional controller applications on top of Faucet, so requiring Docker would get in the way...
Please let me know if there is anything I can do to help. I'm willing to test any changes in any environment I can reproduce.
Test Runs Outside Docker
All tests run right after the other on the same guest (Ubuntu 16.04 on VMware, specs at end of this description).
Pass 1 - 12 Errors, 1 Failed
faucet-1.log.txt
ERROR: __main__.FaucetUntaggedACLTest.test_port5001_blocked (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded

ERROR: __main__.FaucetTaggedControlPlaneTest.test_ping_controller (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded

ERROR: __main__.FaucetUntaggedSameVlanIPv6RouteTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded

ERROR: __main__.FaucetUntaggedACLTest.test_port5002_unblocked (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded

ERROR: __main__.FaucetUntaggedHostMoveTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded

ERROR: __main__.FaucetUntaggedACLMirrorTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded

ERROR: __main__.FaucetUntaggedControlPlaneTest.test_ping_controller (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded

ERROR: __main__.FaucetTaggedControlPlaneTest.test_tagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded

ERROR: __main__.FaucetUntaggedMirrorTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded

ERROR: __main__.FaucetUntaggedOutputTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded

ERROR: __main__.FaucetUntaggedTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded

ERROR: __main__.FaucetTaggedAndUntaggedVlanTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded

FAIL: __main__.FaucetUntaggedMaxHostsTest.test_untagged (subunit.RemotedTestCase)
AssertionError: 2 != 3

Pass 2 - 1 Failed
faucet-2.log.txt
FAIL: __main__.FaucetUntaggedHUPTest.test_untagged (subunit.RemotedTestCase)
AssertionError: 0 != 8.333333333333334

Pass 3 - All Passed
faucet-3.log.txt
Pass 4 - All Passed
faucet-4.log.txt
Pass 5 - 1 Failed
faucet-5.log.txt
FAIL: test_untagged (__main__.FaucetSingleUntaggedIPv4RouteTest)
AssertionError: None is not true

Pass 6 - 1 Error
faucet-6.log.txt
ERROR: __main__.FaucetUntaggedNoVLanUnicastFloodTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded

Pass 7 - 4 Errors
faucet-7.log.txt
ERROR: __main__.FaucetTaggedTest.test_tagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded

ERROR: __main__.FaucetTaggedAndUntaggedTest.test_seperate_untagged_tagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded

ERROR: __main__.FaucetUntaggedACLTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded

ERROR: __main__.FaucetTaggedAndUntaggedVlanTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded

Pass 8 - 1 Error (Mininet exited in checkStartup, see log)
faucet-8.log.txt
ERROR: __main__.FaucetMultipleDPTaggedTest.test_tagged (subunit.RemotedTestCase)
SystemExit: 1

Pass 9 - 2 Failed
faucet-9.log.txt
FAIL: __main__.FaucetUntaggedHostPermanentLearnTest.test_untagged (subunit.RemotedTestCase)
AssertionError: 100.0 != 50.0

FAIL: __main__.FaucetUntaggedMaxHostsTest.test_untagged (subunit.RemotedTestCase)
AssertionError: 2 != 3

Pass 10 - Passed
faucet-10.log.txt
System Information
Host: Ubuntu 14.04 64bit, AMD FX 8320 8-core with 32GB RAM
VMware: VMware Workstation 12 Pro v12.1.1 build-3770994
Desktop Guest (VMware): Ubuntu 16.04 64bit, 8-cores, 8GB RAM
Server Guest(VMware): Ubuntu 16.04 64bit, 8-cores, 4GB RAM
VirtualBox: VirtualBox v5.0.10 r104061
Server Guest (VirtualBox): Ubuntu 16.04 64bit, 1-core, 4GB RAM

including Faucet-dev mailing list
On Wed, Aug 17, 2016 at 10:21 AM, Leo Scott<EMAIL_ADDRESS>wrote:

I've been trying to get the faucet_mininet_test.py tests running outside
a docker container and have all the software requirements installed. The
problem is that some tests will fail intermittently and almost seem like it
is due to race conditions. This occurs on:

Ubuntu 14.04 host > VMware WS 12 > Ubuntu 16.04 desktop guest
Ubuntu 14.04 host > VMware WS 12 > Ubuntu 16.04 server guest (fresh
install for this test)
Ubuntu 14.04 host > Virtualbox 5 > Ubuntu 16.04 server guest (fresh
install for this test)

However, the tests always seem to pass when run in the docker container
(built locally from v1_0-265-g20168ee in the onfsd/faucet fork, as per
README.docker.md). This works on:

Ubuntu 14.04 host > VMware WS 12 > Ubuntu 16.04 desktop guest >
docker > reannz/faucet-test
Ubuntu 14.04 host > docker > reannz/faucet-test

Since this is working in docker on my Ubuntu 16.04 desktop guest, it
should work outside the docker as well. The software requirements come from
faucet_mininet_test.py itself.
However, when run outside the docker container, sometimes the tests pass,
but most of the time it does not. I ran 10 tests in a row and recorded
their results (only test and final exception provided in ticket
description, attached full logs). Passes 3, 4, and 10 passed the tests
completely, the rest failed in some manner. This would suggest that my
checked out version of faucet can function properly on a VM.
I did notice in the docker, however, that Mininet complains that it can't
make all the sysctl calls it needs:
================= Starting OVS ==================

/etc/openvswitch/conf.db does not exist
Creating empty database /etc/openvswitch/conf.db
Starting ovsdb-server
Configuring Open vSwitch system IDs
Starting ovs-vswitchd
Enabling remote OVSDB managers
=========== Running faucet unit tests ===========
test_tagged (faucet_mininet_test.FaucetMultipleDPTaggedTest) ... *** Error setting resource limits. Mininet's performance may be affected.
t4ds1h1 t4ds1h1-eth0.100:s14d-eth1
[...]

This may point to some weirdness where the test works under Docker
conditions with reduced resources, but not directly on a VM, even the VM
running the Docker instance. I've tried modifying the tests to run with
user-mode OVS only, but got similar results. Since the Docker was run in
privileged mode, I would guess that it has access to the kernel DP anyway.
I hope this information helps. I'm in the process of writing tutorials on
setting up the latest dev version of Faucet after my last articles on
covering the Ryu API and creating a Ryu controller application based in
part on the table structure used in Faucet on Inside-OpenFlow.com.
In any case, I would rather write instructions to make this run without
having to use Docker and I always try to have the reader run any tests
supplied with manually installed software first to ensure software is
installed properly before continuing to usage instructions. I plan on
covering additional controller applications on top of Faucet, so requiring
Docker would get in the way...
Please let me know if there is anything I can do to help. I'm willing to
test any changes in any environment I can reproduce.
Test Runs Outside Docker
All tests run right after the other on the same guest (Ubuntu 16.04 on
VMware, specs at end of this description).
Pass 1 - 12 Errors, 1 Failed
faucet-1.log.txt
https://github.com/onfsdn/faucet/files/423083/faucet-1.log.txt
ERROR: main.FaucetUntaggedACLTest.test_port5001_blocked (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetTaggedControlPlaneTest.test_ping_controller (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetUntaggedSameVlanIPv6RouteTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetUntaggedACLTest.test_port5002_unblocked (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetUntaggedHostMoveTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetUntaggedACLMirrorTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetUntaggedControlPlaneTest.test_ping_controller (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetTaggedControlPlaneTest.test_tagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetUntaggedMirrorTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetUntaggedOutputTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetUntaggedTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetTaggedAndUntaggedVlanTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
FAIL: main.FaucetUntaggedMaxHostsTest.test_untagged (subunit.RemotedTestCase)
AssertionError: 2 != 3
Pass 2 - 1 Failed
faucet-2.log.txt
https://github.com/onfsdn/faucet/files/423084/faucet-2.log.txt
FAIL: main.FaucetUntaggedHUPTest.test_untagged (subunit.RemotedTestCase)
AssertionError: 0 != 8.333333333333334
Pass 3 - All Passed
faucet-3.log.txt
https://github.com/onfsdn/faucet/files/423085/faucet-3.log.txt
Pass 4 - All Passed
faucet-4.log.txt
https://github.com/onfsdn/faucet/files/423086/faucet-4.log.txt
Pass 5 - 1 Failed
faucet-5.log.txt
https://github.com/onfsdn/faucet/files/423090/faucet-5.log.txt
FAIL: test_untagged (main.FaucetSingleUntaggedIPv4RouteTest)
AssertionError: None is not true
Pass 6 - 1 Error
faucet-6.log.txt
https://github.com/onfsdn/faucet/files/423091/faucet-6.log.txt
ERROR: main.FaucetUntaggedNoVLanUnicastFloodTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
Pass 7 - 4 Errors
faucet-7.log.txt
https://github.com/onfsdn/faucet/files/423092/faucet-7.log.txt
ERROR: main.FaucetTaggedTest.test_tagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetTaggedAndUntaggedTest.test_seperate_untagged_tagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetUntaggedACLTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetTaggedAndUntaggedVlanTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
Pass 8 - 1 Error (Mininet exited in checkStartup, see log)
faucet-8.log.txt
https://github.com/onfsdn/faucet/files/423094/faucet-8.log.txt
ERROR: main.FaucetMultipleDPTaggedTest.test_tagged (subunit.RemotedTestCase)
SystemExit: 1
Pass 9 - 2 Failed
faucet-9.log.txt
https://github.com/onfsdn/faucet/files/423095/faucet-9.log.txt
FAIL: main.FaucetUntaggedHostPermanentLearnTest.test_untagged (subunit.RemotedTestCase)
AssertionError: 100.0 != 50.0
FAIL: main.FaucetUntaggedMaxHostsTest.test_untagged (subunit.RemotedTestCase)
AssertionError: 2 != 3
Pass 10 - Passed
faucet-10.log.txt
https://github.com/onfsdn/faucet/files/423096/faucet-10.log.txt
System Information
Host: Ubuntu 14.04 64bit, AMD FX 8320 8-core with 32GB RAM
VMware: VMware Workstation 12 Pro v12.1.1 build-3770994
Desktop Guest (VMware): Ubuntu 16.04 64bit, 8-cores, 8GB RAM
Server Guest(VMware): Ubuntu 16.04 64bit, 8-cores, 4GB RAM
VirtualBox: VirtualBox v5.0.10 r104061
Server Guest (VirtualBox): Ubuntu 16.04 64bit, 1-core, 4GB RAM
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/onfsdn/faucet/issues/10, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABmf8yXia9YLlFczt-GSQWjS6hGbSB_1ks5qg0MAgaJpZM4Jmr2l
.

Thanks for the very thorough investigation!
Most of the failures here described seem to be communicating with the ofctl
module (which is used by the tests to access the OF channel to the test
switch, to make sure it has the right flows for a given test). I presume
what's going on is we are failing to get a free port (certainly in the
docker environment there is much less competition so no surprise it always
passes there).
I actually think the right path is actually running tests under docker so
that the test environment is sterile. I also see a lot of sites prefer to
run FAUCET inside a container as best practice, so I suggest actually
depending on docker is not just fine but preferred.
On Thu, Aug 18, 2016 at 7:43 AM, Shivaram Mysore<EMAIL_ADDRESS>wrote:

including Faucet-dev mailing list
On Wed, Aug 17, 2016 at 10:21 AM, Leo Scott<EMAIL_ADDRESS>wrote:

I've been trying to get the faucet_mininet_test.py tests running outside
a docker container and have all the software requirements installed. The
problem is that some tests will fail intermittently and almost seem like it
is due to race conditions. This occurs on:

Ubuntu 14.04 host > VMware WS 12 > Ubuntu 16.04 desktop guest
Ubuntu 14.04 host > VMware WS 12 > Ubuntu 16.04 server guest (fresh
install for this test)
Ubuntu 14.04 host > Virtualbox 5 > Ubuntu 16.04 server guest (fresh
install for this test)

However, the tests always seem to pass when run in the docker container
(built locally from v1_0-265-g20168ee in the onfsd/faucet fork, as per
README.docker.md). This works on:

Ubuntu 14.04 host > VMware WS 12 > Ubuntu 16.04 desktop guest >
docker > reannz/faucet-test
Ubuntu 14.04 host > docker > reannz/faucet-test

Since this is working in docker on my Ubuntu 16.04 desktop guest, it
should work outside the docker as well. The software requirements come from
faucet_mininet_test.py itself.
However, when run outside the docker container, sometimes the tests pass,
but most of the time it does not. I ran 10 tests in a row and recorded
their results (only test and final exception provided in ticket
description, attached full logs). Passes 3, 4, and 10 passed the tests
completely, the rest failed in some manner. This would suggest that my
checked out version of faucet can function properly on a VM.
I did notice in the docker, however, that Mininet complains that it can't
make all the sysctl calls it needs:
================= Starting OVS ==================

/etc/openvswitch/conf.db does not exist
Creating empty database /etc/openvswitch/conf.db
Starting ovsdb-server
Configuring Open vSwitch system IDs
Starting ovs-vswitchd
Enabling remote OVSDB managers
=========== Running faucet unit tests ===========
test_tagged (faucet_mininet_test.FaucetMultipleDPTaggedTest) ... *** Error setting resource limits. Mininet's performance may be affected.
t4ds1h1 t4ds1h1-eth0.100:s14d-eth1
[...]

This may point to some weirdness where the test works under Docker
conditions with reduced resources, but not directly on a VM, even the VM
running the Docker instance. I've tried modifying the tests to run with
user-mode OVS only, but got similar results. Since the Docker was run in
privileged mode, I would guess that it has access to the kernel DP anyway.
I hope this information helps. I'm in the process of writing tutorials on
setting up the latest dev version of Faucet after my last articles on
covering the Ryu API and creating a Ryu controller application based in
part on the table structure used in Faucet on Inside-OpenFlow.com.
In any case, I would rather write instructions to make this run without
having to use Docker and I always try to have the reader run any tests
supplied with manually installed software first to ensure software is
installed properly before continuing to usage instructions. I plan on
covering additional controller applications on top of Faucet, so requiring
Docker would get in the way...
Please let me know if there is anything I can do to help. I'm willing to
test any changes in any environment I can reproduce.
Test Runs Outside Docker
All tests run right after the other on the same guest (Ubuntu 16.04 on
VMware, specs at end of this description).
Pass 1 - 12 Errors, 1 Failed
faucet-1.log.txt
https://github.com/onfsdn/faucet/files/423083/faucet-1.log.txt
ERROR: main.FaucetUntaggedACLTest.test_port5001_blocked (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetTaggedControlPlaneTest.test_ping_controller (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetUntaggedSameVlanIPv6RouteTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetUntaggedACLTest.test_port5002_unblocked (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetUntaggedHostMoveTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetUntaggedACLMirrorTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetUntaggedControlPlaneTest.test_ping_controller (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetTaggedControlPlaneTest.test_tagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetUntaggedMirrorTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetUntaggedOutputTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetUntaggedTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetTaggedAndUntaggedVlanTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
FAIL: main.FaucetUntaggedMaxHostsTest.test_untagged (subunit.RemotedTestCase)
AssertionError: 2 != 3
Pass 2 - 1 Failed
faucet-2.log.txt
https://github.com/onfsdn/faucet/files/423084/faucet-2.log.txt
FAIL: main.FaucetUntaggedHUPTest.test_untagged (subunit.RemotedTestCase)
AssertionError: 0 != 8.333333333333334
Pass 3 - All Passed
faucet-3.log.txt
https://github.com/onfsdn/faucet/files/423085/faucet-3.log.txt
Pass 4 - All Passed
faucet-4.log.txt
https://github.com/onfsdn/faucet/files/423086/faucet-4.log.txt
Pass 5 - 1 Failed
faucet-5.log.txt
https://github.com/onfsdn/faucet/files/423090/faucet-5.log.txt
FAIL: test_untagged (main.FaucetSingleUntaggedIPv4RouteTest)
AssertionError: None is not true
Pass 6 - 1 Error
faucet-6.log.txt
https://github.com/onfsdn/faucet/files/423091/faucet-6.log.txt
ERROR: main.FaucetUntaggedNoVLanUnicastFloodTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
Pass 7 - 4 Errors
faucet-7.log.txt
https://github.com/onfsdn/faucet/files/423092/faucet-7.log.txt
ERROR: main.FaucetTaggedTest.test_tagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetTaggedAndUntaggedTest.test_seperate_untagged_tagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetUntaggedACLTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetTaggedAndUntaggedVlanTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
Pass 8 - 1 Error (Mininet exited in checkStartup, see log)
faucet-8.log.txt
https://github.com/onfsdn/faucet/files/423094/faucet-8.log.txt
ERROR: main.FaucetMultipleDPTaggedTest.test_tagged (subunit.RemotedTestCase)
SystemExit: 1
Pass 9 - 2 Failed
faucet-9.log.txt
https://github.com/onfsdn/faucet/files/423095/faucet-9.log.txt
FAIL: main.FaucetUntaggedHostPermanentLearnTest.test_untagged (subunit.RemotedTestCase)
AssertionError: 100.0 != 50.0
FAIL: main.FaucetUntaggedMaxHostsTest.test_untagged (subunit.RemotedTestCase)
AssertionError: 2 != 3
Pass 10 - Passed
faucet-10.log.txt
https://github.com/onfsdn/faucet/files/423096/faucet-10.log.txt
System Information
Host: Ubuntu 14.04 64bit, AMD FX 8320 8-core with 32GB RAM
VMware: VMware Workstation 12 Pro v12.1.1 build-3770994
Desktop Guest (VMware): Ubuntu 16.04 64bit, 8-cores, 8GB RAM
Server Guest(VMware): Ubuntu 16.04 64bit, 8-cores, 4GB RAM
VirtualBox: VirtualBox v5.0.10 r104061
Server Guest (VirtualBox): Ubuntu 16.04 64bit, 1-core, 4GB RAM
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/onfsdn/faucet/issues/10, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABmf8yXia9YLlFczt-GSQWjS6hGbSB_1ks5qg0MAgaJpZM4Jmr2l
.

--
Latest info about Ryu Faucet is available @ http://onfsdn.github.io/
faucet/
You received this message because you are subscribed to the Google Groups
"Faucet Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to<EMAIL_ADDRESS>To post to this group, send email to<EMAIL_ADDRESS>To view this discussion on the web visit https://groups.google.com/a/
openflowsdn.org/d/msgid/faucet-dev/CAJRY%2BjqMLNY3tMSp0taudNLQ_
7vFE2pzGbh14Me9hF5fiSyASg%40mail.gmail.com
https://groups.google.com/a/openflowsdn.org/d/msgid/faucet-dev/CAJRY%2BjqMLNY3tMSp0taudNLQ_7vFE2pzGbh14Me9hF5fiSyASg%40mail.gmail.com?utm_medium=email&utm_source=footer
.

I've found a way to reproduce this issue inside the docker container. As mentioned in #13, the faucet tests run inside the Docker container skip the version requirements and, looking at the installation log, you can see that the pip install /faucet-src command fails on several dependencies:
[...]
Building wheels for collected packages: ryu-faucet, pyyaml, ipaddr, concurrencytest, python-mimeparse
  Running setup.py bdist_wheel for ryu-faucet: started
  Running setup.py bdist_wheel for ryu-faucet: finished with status 'error'
  Complete output from command /usr/bin/python -u -c "import setuptools, tokenize;__file__='/tmp/pip-wCWE_X-build/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\
n'), __file__, 'exec'))" bdist_wheel -d /tmp/tmpIZxVVRpip-wheel- --python-tag cp27:
  usage: -c [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
     or: -c --help [cmd1 cmd2 ...]
     or: -c --help-commands
     or: -c cmd --help

  error: invalid command 'bdist_wheel'

  ----------------------------------------
  Failed building wheel for ryu-faucet
  Running setup.py clean for ryu-faucet
  Running setup.py bdist_wheel for pyyaml: started
  Running setup.py bdist_wheel for pyyaml: finished with status 'error'
  Complete output from command /usr/bin/python -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-kDXIFg/pyyaml/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r
\n', '\n'), __file__, 'exec'))" bdist_wheel -d /tmp/tmpUht22Bpip-wheel- --python-tag cp27:
  usage: -c [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
     or: -c --help [cmd1 cmd2 ...]
     or: -c --help-commands
     or: -c cmd --help

  error: invalid command 'bdist_wheel'

  ----------------------------------------
  Failed building wheel for pyyaml
  Running setup.py clean for pyyaml
  Running setup.py bdist_wheel for ipaddr: started
  Running setup.py bdist_wheel for ipaddr: finished with status 'error'
  Complete output from command /usr/bin/python -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-kDXIFg/ipaddr/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r
\n', '\n'), __file__, 'exec'))" bdist_wheel -d /tmp/tmp5RhV3epip-wheel- --python-tag cp27:
  Failed building wheel for ipaddr
  usage: -c [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
     or: -c --help [cmd1 cmd2 ...]
     or: -c --help-commands
     or: -c cmd --help

  error: invalid command 'bdist_wheel'

  ----------------------------------------
  Running setup.py clean for ipaddr
  Running setup.py bdist_wheel for concurrencytest: started
  Running setup.py bdist_wheel for concurrencytest: finished with status 'error'
  Complete output from command /usr/bin/python -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-kDXIFg/concurrencytest/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().re
place('\r\n', '\n'), __file__, 'exec'))" bdist_wheel -d /tmp/tmplPJP1Mpip-wheel- --python-tag cp27:
  Failed building wheel for concurrencytest
  usage: -c [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
     or: -c --help [cmd1 cmd2 ...]
     or: -c --help-commands
     or: -c cmd --help

  error: invalid command 'bdist_wheel'

  ----------------------------------------
  Running setup.py clean for concurrencytest
  Running setup.py bdist_wheel for python-mimeparse: started
  Running setup.py bdist_wheel for python-mimeparse: finished with status 'error'
  Complete output from command /usr/bin/python -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-kDXIFg/python-mimeparse/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().r
eplace('\r\n', '\n'), __file__, 'exec'))" bdist_wheel -d /tmp/tmpVPfM9Cpip-wheel- --python-tag cp27:
  usage: -c [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
     or: -c --help [cmd1 cmd2 ...]
     or: -c --help-commands
     or: -c cmd --help

  error: invalid command 'bdist_wheel'

  ----------------------------------------
  Failed building wheel for python-mimeparse
  Running setup.py clean for python-mimeparse
Failed to build ryu-faucet pyyaml ipaddr concurrencytest python-mimeparse
Installing collected packages: pyyaml, python-dateutil, requests, influxdb, ipaddr, extras, python-mimeparse, fixtures, linecache2, traceback2, unittest2, testtools, python-subunit, concurrencytest, ryu-f
aucet
  Running setup.py install for pyyaml: started
    Running setup.py install for pyyaml: finished with status 'done'
  Running setup.py install for ipaddr: started
    Running setup.py install for ipaddr: finished with status 'done'
  Running setup.py install for python-mimeparse: started
    Running setup.py install for python-mimeparse: finished with status 'done'
  Running setup.py install for concurrencytest: started
    Running setup.py install for concurrencytest: finished with status 'done'
  Running setup.py install for ryu-faucet: started
    Running setup.py install for ryu-faucet: finished with status 'done'
Successfully installed concurrencytest-0.1.2 extras-1.0.0 fixtures-3.0.0 influxdb-3.0.0 ipaddr-2.1.11 linecache2-1.0.0 python-dateutil-2.5.3 python-mimeparse-1.5.2 python-subunit-1.2.0 pyyaml-3.11 request
s-2.11.1 ryu-faucet-1.0 testtools-2.2.0 traceback2-1.4.0 unittest2-1.1.0
You are using pip version 8.1.1, however version 8.1.2 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.

docker-build-log-master.txt
Running the Docker container with these installation errors result in tests passing.
However, when pip is updated (which requires uninstalling the python-pip apt package and installing manually by getting get-pip.py), the installation can actually complete with no errors (this is from https://github.com/inside-openflow/faucet/tree/fix-docker-version-check that I wrote for #13):
[...]
Building wheels for collected packages: ryu-faucet, pyyaml, ipaddr, concurrencytest, python-mimeparse
  Running setup.py bdist_wheel for ryu-faucet: started
  Running setup.py bdist_wheel for ryu-faucet: finished with status 'done'
  Stored in directory: /root/.cache/pip/wheels/7e/19/b3/9c7266b6114dc8b35f8a6a0ce8f2c556ebce0c1a4d1c3
4f8e5
  Running setup.py bdist_wheel for pyyaml: started
  Running setup.py bdist_wheel for pyyaml: finished with status 'done'
  Stored in directory: /root/.cache/pip/wheels/4a/bf/14/d79994d19a59d4f73efdafb8682961f582d45ed6b4594
20346
  Running setup.py bdist_wheel for ipaddr: started
  Running setup.py bdist_wheel for ipaddr: finished with status 'done'
  Stored in directory: /root/.cache/pip/wheels/58/de/20/928e64e591abff7374a8e77e19a765b1572c25d9102c4
2f8b2
  Running setup.py bdist_wheel for concurrencytest: started
  Running setup.py bdist_wheel for concurrencytest: finished with status 'done'
  Stored in directory: /root/.cache/pip/wheels/06/e6/0f/b995e05cdebba9e02bb83780aa09310762b230b809618
f57e7
  Running setup.py bdist_wheel for python-mimeparse: started
  Running setup.py bdist_wheel for python-mimeparse: finished with status 'done'
  Stored in directory: /root/.cache/pip/wheels/3b/c4/a2/2cc8028661bdac35628e0c25d6e6b90946a3b4279c7d7
0cb69
Successfully built ryu-faucet pyyaml ipaddr concurrencytest python-mimeparse
Installing collected packages: pyyaml, python-dateutil, requests, influxdb, ipaddr, extras, python-mi
meparse, fixtures, linecache2, traceback2, unittest2, testtools, python-subunit, concurrencytest, ryu
-faucet
Successfully installed concurrencytest-0.1.2 extras-1.0.0 fixtures-3.0.0 influxdb-3.0.0 ipaddr-2.1.11
 linecache2-1.0.0 python-dateutil-2.5.3 python-mimeparse-1.5.2 python-subunit-1.2.0 pyyaml-3.11 reque
sts-2.11.1 ryu-faucet-1.0 testtools-2.2.0 traceback2-1.4.0 unittest2-1.1.0

docker-build-log-branch.txt
So that get's us to the point where we can run the tests as they are documented the way they should be run (see #13).
Currently, the tests are designed to be run concurrently, and the README reflects this. I found that if I ran the docker inside a VM given enough resources (8gb, 8 cores), the tests pass just fine in the container when called as ./faucet_mininet_tests.py (rather than python -m unittest -v faucet_mininet_test), but if the same docker is run in a VM with only a single core, the errors start popping up as reported in this ticket. This suggests an issue with running all the tests concurrently, even in a Docker. It may seem odd that the docker would be run with a single core in a production environment, but if there are issues running on a single core, there may be issues in the field that are present, but only show in very high load situations.
I suggest that either the runtests.sh file be updated to reflect the current state of the documentation (running so version checks and concurrent tests are performed) and then concurrency issues can be resolved in the pristine environment. Otherwise, the concurrency may need to be dropped entirely from the tests and the README updated to reflect this. Either way, if the Docker container is going to be the preferred method of running Faucet, the Docker environment and the documentation should match. In any case, I was able to reproduce the issue in a container, so this occurs even in a pristine environment.

Just to follow up this thread. We have made numerous fixes to the tests to
make them more reliable both inside and outside Docker (and thank you for
the fix re pylint version). I believe the tests are now in good shape -
please do let us know if there are any further flake cases.
Thanks,
On Tue, Aug 23, 2016 at 8:19 AM, Josh Bailey<EMAIL_ADDRESS>wrote:

Thanks for the very thorough investigation!
Most of the failures here described seem to be communicating with the
ofctl module (which is used by the tests to access the OF channel to the
test switch, to make sure it has the right flows for a given test). I
presume what's going on is we are failing to get a free port (certainly in
the docker environment there is much less competition so no surprise it
always passes there).
I actually think the right path is actually running tests under docker so
that the test environment is sterile. I also see a lot of sites prefer to
run FAUCET inside a container as best practice, so I suggest actually
depending on docker is not just fine but preferred.
On Thu, Aug 18, 2016 at 7:43 AM, Shivaram Mysore <
<EMAIL_ADDRESS>wrote:

including Faucet-dev mailing list
On Wed, Aug 17, 2016 at 10:21 AM, Leo Scott<EMAIL_ADDRESS>wrote:

I've been trying to get the faucet_mininet_test.py tests running
outside a docker container and have all the software requirements
installed. The problem is that some tests will fail intermittently and
almost seem like it is due to race conditions. This occurs on:

Ubuntu 14.04 host > VMware WS 12 > Ubuntu 16.04 desktop guest
Ubuntu 14.04 host > VMware WS 12 > Ubuntu 16.04 server guest
(fresh install for this test)
Ubuntu 14.04 host > Virtualbox 5 > Ubuntu 16.04 server guest
(fresh install for this test)

However, the tests always seem to pass when run in the docker container
(built locally from v1_0-265-g20168ee in the onfsd/faucet fork, as per
README.docker.md). This works on:

Ubuntu 14.04 host > VMware WS 12 > Ubuntu 16.04 desktop guest >
docker > reannz/faucet-test
Ubuntu 14.04 host > docker > reannz/faucet-test

Since this is working in docker on my Ubuntu 16.04 desktop guest, it
should work outside the docker as well. The software requirements come from
faucet_mininet_test.py itself.
However, when run outside the docker container, sometimes the tests
pass, but most of the time it does not. I ran 10 tests in a row and
recorded their results (only test and final exception provided in ticket
description, attached full logs). Passes 3, 4, and 10 passed the tests
completely, the rest failed in some manner. This would suggest that my
checked out version of faucet can function properly on a VM.
I did notice in the docker, however, that Mininet complains that it
can't make all the sysctl calls it needs:
================= Starting OVS ==================

/etc/openvswitch/conf.db does not exist
Creating empty database /etc/openvswitch/conf.db
Starting ovsdb-server
Configuring Open vSwitch system IDs
Starting ovs-vswitchd
Enabling remote OVSDB managers
=========== Running faucet unit tests ===========
test_tagged (faucet_mininet_test.FaucetMultipleDPTaggedTest) ... *** Error setting resource limits. Mininet's performance may be affected.
t4ds1h1 t4ds1h1-eth0.100:s14d-eth1
[...]

This may point to some weirdness where the test works under Docker
conditions with reduced resources, but not directly on a VM, even the VM
running the Docker instance. I've tried modifying the tests to run with
user-mode OVS only, but got similar results. Since the Docker was run in
privileged mode, I would guess that it has access to the kernel DP anyway.
I hope this information helps. I'm in the process of writing tutorials
on setting up the latest dev version of Faucet after my last articles on
covering the Ryu API and creating a Ryu controller application based in
part on the table structure used in Faucet on Inside-OpenFlow.com.
In any case, I would rather write instructions to make this run without
having to use Docker and I always try to have the reader run any tests
supplied with manually installed software first to ensure software is
installed properly before continuing to usage instructions. I plan on
covering additional controller applications on top of Faucet, so requiring
Docker would get in the way...
Please let me know if there is anything I can do to help. I'm willing to
test any changes in any environment I can reproduce.
Test Runs Outside Docker
All tests run right after the other on the same guest (Ubuntu 16.04 on
VMware, specs at end of this description).
Pass 1 - 12 Errors, 1 Failed
faucet-1.log.txt
https://github.com/onfsdn/faucet/files/423083/faucet-1.log.txt
ERROR: main.FaucetUntaggedACLTest.test_port5001_blocked (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetTaggedControlPlaneTest.test_ping_controller (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetUntaggedSameVlanIPv6RouteTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetUntaggedACLTest.test_port5002_unblocked (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetUntaggedHostMoveTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetUntaggedACLMirrorTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetUntaggedControlPlaneTest.test_ping_controller (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetTaggedControlPlaneTest.test_tagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetUntaggedMirrorTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetUntaggedOutputTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetUntaggedTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetTaggedAndUntaggedVlanTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
FAIL: main.FaucetUntaggedMaxHostsTest.test_untagged (subunit.RemotedTestCase)
AssertionError: 2 != 3
Pass 2 - 1 Failed
faucet-2.log.txt
https://github.com/onfsdn/faucet/files/423084/faucet-2.log.txt
FAIL: main.FaucetUntaggedHUPTest.test_untagged (subunit.RemotedTestCase)
AssertionError: 0 != 8.333333333333334
Pass 3 - All Passed
faucet-3.log.txt
https://github.com/onfsdn/faucet/files/423085/faucet-3.log.txt
Pass 4 - All Passed
faucet-4.log.txt
https://github.com/onfsdn/faucet/files/423086/faucet-4.log.txt
Pass 5 - 1 Failed
faucet-5.log.txt
https://github.com/onfsdn/faucet/files/423090/faucet-5.log.txt
FAIL: test_untagged (main.FaucetSingleUntaggedIPv4RouteTest)
AssertionError: None is not true
Pass 6 - 1 Error
faucet-6.log.txt
https://github.com/onfsdn/faucet/files/423091/faucet-6.log.txt
ERROR: main.FaucetUntaggedNoVLanUnicastFloodTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
Pass 7 - 4 Errors
faucet-7.log.txt
https://github.com/onfsdn/faucet/files/423092/faucet-7.log.txt
ERROR: main.FaucetTaggedTest.test_tagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetTaggedAndUntaggedTest.test_seperate_untagged_tagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetUntaggedACLTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
ERROR: main.FaucetTaggedAndUntaggedVlanTest.test_untagged (subunit.RemotedTestCase)
ValueError: No JSON object could be decoded
Pass 8 - 1 Error (Mininet exited in checkStartup, see log)
faucet-8.log.txt
https://github.com/onfsdn/faucet/files/423094/faucet-8.log.txt
ERROR: main.FaucetMultipleDPTaggedTest.test_tagged (subunit.RemotedTestCase)
SystemExit: 1
Pass 9 - 2 Failed
faucet-9.log.txt
https://github.com/onfsdn/faucet/files/423095/faucet-9.log.txt
FAIL: main.FaucetUntaggedHostPermanentLearnTest.test_untagged (subunit.RemotedTestCase)
AssertionError: 100.0 != 50.0
FAIL: main.FaucetUntaggedMaxHostsTest.test_untagged (subunit.RemotedTestCase)
AssertionError: 2 != 3
Pass 10 - Passed
faucet-10.log.txt
https://github.com/onfsdn/faucet/files/423096/faucet-10.log.txt
System Information
Host: Ubuntu 14.04 64bit, AMD FX 8320 8-core with 32GB RAM
VMware: VMware Workstation 12 Pro v12.1.1 build-3770994
Desktop Guest (VMware): Ubuntu 16.04 64bit, 8-cores, 8GB RAM
Server Guest(VMware): Ubuntu 16.04 64bit, 8-cores, 4GB RAM
VirtualBox: VirtualBox v5.0.10 r104061
Server Guest (VirtualBox): Ubuntu 16.04 64bit, 1-core, 4GB RAM
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/onfsdn/faucet/issues/10, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABmf8yXia9YLlFczt-GSQWjS6hGbSB_1ks5qg0MAgaJpZM4Jmr2l
.

--
Latest info about Ryu Faucet is available @
http://onfsdn.github.io/faucet/
You received this message because you are subscribed to the Google Groups
"Faucet Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to<EMAIL_ADDRESS>To post to this group, send email to<EMAIL_ADDRESS>To view this discussion on the web visit https://groups.google.com/a/op
enflowsdn.org/d/msgid/faucet-dev/CAJRY%2BjqMLNY3tMSp0taudNL
Q_7vFE2pzGbh14Me9hF5fiSyASg%40mail.gmail.com
https://groups.google.com/a/openflowsdn.org/d/msgid/faucet-dev/CAJRY%2BjqMLNY3tMSp0taudNLQ_7vFE2pzGbh14Me9hF5fiSyASg%40mail.gmail.com?utm_medium=email&utm_source=footer
.

I seem to be having more issues with the docker tests now. Inside a fresh Ubuntu 16.04 VM (4gb, 4cores) with Docker installed, then having the Faucet test docker image built and run inside that VM, the first time I got this:
======================================================================
ERROR: __main__.FaucetUntaggedControlPlaneTest.test_untagged (subunit.RemotedTestCase)
__main__.FaucetUntaggedControlPlaneTest.test_untagged
----------------------------------------------------------------------
_StringException: Traceback (most recent call last):
  File "./faucet_mininet_test.py", line 626, in test_untagged
    assert os.stat(self.monitor_ports_file).st_size > 0
OSError: [Errno 2] No such file or directory: '/tmp/tmpjumRlm/ports.txt'

======================================================================
ERROR: __main__.FaucetUntaggedTest.test_untagged (subunit.RemotedTestCase)
__main__.FaucetUntaggedTest.test_untagged
----------------------------------------------------------------------
_StringException: Traceback (most recent call last):
  File "./faucet_mininet_test.py", line 626, in test_untagged
    assert os.stat(self.monitor_ports_file).st_size > 0
OSError: [Errno 2] No such file or directory: '/tmp/tmp2sFHCl/ports.txt'

======================================================================
ERROR: __main__.FaucetUntaggedACLTest.test_untagged (subunit.RemotedTestCase)
__main__.FaucetUntaggedACLTest.test_untagged
----------------------------------------------------------------------
_StringException: Traceback (most recent call last):
  File "./faucet_mininet_test.py", line 626, in test_untagged
    assert os.stat(self.monitor_ports_file).st_size > 0
OSError: [Errno 2] No such file or directory: '/tmp/tmp1fY7Dt/ports.txt'

----------------------------------------------------------------------
Ran 22 tests in 47.209s

The second time stalled for half an hour and I had to press Ctrl+C:
*** Results: 16% dropped (10/12 received)
*** Ping: testing ping reachability
u7a1 -> u7a2 u7a3 u7a4
u7a2 -> u7a1 u7a3 u7a4
u7a3 -> u7a1 u7a2 u7a4
u7a4 -> u7a1 u7a2 u7a3
*** Results: 0% dropped (12/12 received)
...
^CTraceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/concurrencytest.py", line 82, in do_fork
    process_suite.run(subunit_result)
  File "/usr/lib/python2.7/unittest/suite.py", line 108, in run
    test(result)
  File "/usr/lib/python2.7/unittest/case.py", line 393, in __call__
    return self.run(*args, **kwds)
  File "/usr/lib/python2.7/unittest/case.py", line 320, in run
    self.setUp()
  File "./faucet_mininet_test.py", line 615, in setUp
    self.start_net()
  File "./faucet_mininet_test.py", line 305, in start_net
    self.net.waitConnected()
  File "build/bdist.linux-x86_64/egg/mininet/net.py", line 193, in waitConnected
    sleep( delay )
KeyboardInterrupt
ETraceback (most recent call last):
  File "./faucet_mininet_test.py", line 1882, in <module>
    run_tests()
  File "./faucet_mininet_test.py", line 1858, in run_tests
    results.append(parallel_runner.run(parallel_suite))
  File "/usr/lib/python2.7/unittest/runner.py", line 151, in run
    test(result)
  File "/usr/local/lib/python2.7/dist-packages/unittest2/suite.py", line 87, in __call__
    return self.run(*args, **kwds)
  File "/usr/local/lib/python2.7/dist-packages/testtools/testsuite.py", line 95, in run
    finished_test = queue.get()
  File "/usr/lib/python2.7/Queue.py", line 168, in get
    self.not_empty.wait()
  File "/usr/lib/python2.7/threading.py", line 340, in wait
    waiter.acquire()
KeyboardInterrupt

real    34m1.055s
user    5m25.540s
sys     0m48.320s

The VM is set up with Ubuntu 16.04 with the following commands:
#!/bin/bash
set -e

apt-get -qy install apt-transport-https ca-certificates
apt-key adv --keyserver hkp://p80.pool.sks-keyservers.net:80 \
  --recv-keys 58118E89F3A912897C070ADBF76221572C52609D
cat >/etc/apt/sources.list.d/docker.list <<EOF
deb https://apt.dockerproject.org/repo ubuntu-xenial main
EOF
apt-get -qy update
apt-get -qy purge lxc-docker || true
apt-get -qy install linux-image-extra-$(uname -r) docker-engine
service docker start

Docker image built and run with:
#!/bin/bash
set -e

cd /faucet-src
docker build -t reannz/faucet-tests -f Dockerfile.tests .
apparmor_parser -R /etc/apparmor.d/usr.sbin.tcpdump || true
modprobe openvswitch
docker run --privileged -ti reannz/faucet-tests

I don't think memory usage is an issue. The VM never utilized more than 2gb of the allocated 4gb RAM.
I'll run the docker tests directly on my workstation outside the fresh VM with docker installed to see if that makes any difference. Note that the docker image was built without any previous cache, as it was a fresh VM that was created for today's test.

I ran the Docker instance directly on my workstation (rather than in a VM) and I get the same freeze as before. I pressed Ctrl+C after half an hour. This seems to be a new issue. Should I write a new ticket then?
full logs:
docker-build-20160831.txt
docker-run-20160831.txt
excerpt:
*** Ping: testing ping reachability
u8c1 -> u8c2 u8c3 u8c4
u8c2 -> u8c1 u8c3 u8c4
u8c3 -> u8c1 u8c2 u8c4
u8c4 -> u8c1 u8c2 u8c3
*** Results: 0% dropped (12/12 received)
..^CTraceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/concurrencytest.py", line 82, in do_fork
    process_suite.run(subunit_result)
  File "/usr/lib/python2.7/unittest/suite.py", line 108, in run
    test(result)
  File "/usr/lib/python2.7/unittest/case.py", line 393, in __call__
    return self.run(*args, **kwds)
  File "/usr/lib/python2.7/unittest/case.py", line 320, in run
    self.setUp()
  File "./faucet_mininet_test.py", line 1197, in setUp
    self.start_net()
  File "./faucet_mininet_test.py", line 305, in start_net
    self.net.waitConnected()
  File "build/bdist.linux-x86_64/egg/mininet/net.py", line 185, in waitConnected
    if switch.connected():
  File "build/bdist.linux-x86_64/egg/mininet/node.py", line 1118, in connected
    uuid, 'is_connected' ):
  File "build/bdist.linux-x86_64/egg/mininet/node.py", line 1081, in vsctl
    return self.cmd( 'ovs-vsctl', *args, **kwargs )
  File "build/bdist.linux-x86_64/egg/mininet/node.py", line 351, in cmd
    return self.waitOutput( verbose )
  File "build/bdist.linux-x86_64/egg/mininet/node.py", line 338, in waitOutput
    data = self.monitor( findPid=findPid )
  File "build/bdist.linux-x86_64/egg/mininet/node.py", line 305, in monitor
    data = self.read( 1024 )
  File "build/bdist.linux-x86_64/egg/mininet/node.py", line 217, in read
    data = os.read( self.stdout.fileno(), maxbytes - count )
KeyboardInterrupt
ETraceback (most recent call last):
  File "./faucet_mininet_test.py", line 1882, in <module>
    run_tests()
  File "./faucet_mininet_test.py", line 1858, in run_tests
    results.append(parallel_runner.run(parallel_suite))
  File "/usr/lib/python2.7/unittest/runner.py", line 151, in run
    test(result)
  File "/usr/local/lib/python2.7/dist-packages/unittest2/suite.py", line 87, in __call__
    return self.run(*args, **kwds)
  File "/usr/local/lib/python2.7/dist-packages/testtools/testsuite.py", line 95, in run
    finished_test = queue.get()
  File "/usr/lib/python2.7/Queue.py", line 168, in get
    self.not_empty.wait()
  File "/usr/lib/python2.7/threading.py", line 340, in wait
    waiter.acquire()
KeyboardInterrupt

real    31m2.707s
user    6m20.525s
sys     0m58.517s

Container built with --no-cache to ensure the most up-to-date build. Workstation has 32GB RAM and 8 (real) cores, so I doubt resources were an issue.

Hi Leo,
(included<EMAIL_ADDRESS>mailing list as others may also be
interested)
One of our colleagues had a similar problem, when he did not follow Brad's
excellent instructions.
Can you please confirm if you  did:
docker build -t reannz/faucet-tests -f Dockerfile.tests .
apparmor_parser -R /etc/apparmor.d/usr.sbin.tcpdump
modprobe openvswitch
sudo docker run --privileged -ti reannz/faucet-tests
thanks
On Wed, Aug 31, 2016 at 11:14 AM, Leo Scott<EMAIL_ADDRESS>wrote:

I ran the Docker instance directly on my workstation (rather than in a VM)
and I get the same freeze as before. I pressed Ctrl+C after half an hour.
This seems to be a new issue. Should I write a new ticket then?
full logs:
docker-build-20160831.txt
https://github.com/onfsdn/faucet/files/447971/docker-build-20160831.txt
docker-run-20160831.txt
https://github.com/onfsdn/faucet/files/447972/docker-run-20160831.txt
excerpt:
*** Ping: testing ping reachability
u8c1 -> u8c2 u8c3 u8c4
u8c2 -> u8c1 u8c3 u8c4
u8c3 -> u8c1 u8c2 u8c4
u8c4 -> u8c1 u8c2 u8c3
*** Results: 0% dropped (12/12 received)
..^CTraceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/concurrencytest.py", line 82, in do_fork
process_suite.run(subunit_result)
File "/usr/lib/python2.7/unittest/suite.py", line 108, in run
test(result)
File "/usr/lib/python2.7/unittest/case.py", line 393, in call
return self.run(*args, **kwds)
File "/usr/lib/python2.7/unittest/case.py", line 320, in run
self.setUp()
File "./faucet_mininet_test.py", line 1197, in setUp
self.start_net()
File "./faucet_mininet_test.py", line 305, in start_net
self.net.waitConnected()
File "build/bdist.linux-x86_64/egg/mininet/net.py", line 185, in waitConnected
if switch.connected():
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 1118, in connected
uuid, 'is_connected' ):
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 1081, in vsctl
return self.cmd( 'ovs-vsctl', *args, **kwargs )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 351, in cmd
return self.waitOutput( verbose )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 338, in waitOutput
data = self.monitor( findPid=findPid )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 305, in monitor
data = self.read( 1024 )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 217, in read
data = os.read( self.stdout.fileno(), maxbytes - count )
KeyboardInterrupt
ETraceback (most recent call last):
File "./faucet_mininet_test.py", line 1882, in
run_tests()
File "./faucet_mininet_test.py", line 1858, in run_tests
results.append(parallel_runner.run(parallel_suite))
File "/usr/lib/python2.7/unittest/runner.py", line 151, in run
test(result)
File "/usr/local/lib/python2.7/dist-packages/unittest2/suite.py", line 87, in call
return self.run(*args, **kwds)
File "/usr/local/lib/python2.7/dist-packages/testtools/testsuite.py", line 95, in run
finished_test = queue.get()
File "/usr/lib/python2.7/Queue.py", line 168, in get
self.not_empty.wait()
File "/usr/lib/python2.7/threading.py", line 340, in wait
waiter.acquire()
KeyboardInterrupt
real    31m2.707s
user    6m20.525s
sys     0m58.517s
Container built with --no-cache to ensure the most up-to-date build.
Workstation has 32GB RAM and 8 (real) cores, so I doubt resources were an
issue.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/onfsdn/faucet/issues/10#issuecomment-243852272, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABmf8609c-gZ4izyBcBz0mSbb2fIhc6cks5qlcR8gaJpZM4Jmr2l
.

Had just finished my draft to Josh before you sent this. Here it is for the
mailing list (short answer: yes, on two platforms).
Tests fail when following the README.docker.md instructions. Docker image
in privilege mode, with tcpdump apparmor profile removed and openvswitch
module loaded before running. Image built with --no-cache to ensure prior
builds did not affect test.
You can see my complete build and run console log (including commands) in
https://github.com/onfsdn/faucet/issues/10, see my last comment. I am
performing the exact directions in the README.docker.md file (at least as
of this morning). The last comment demonstrates the same issue running the
docker image directly on my workstation (I usually use separate VM
workspaces for different projects, even when running Docker containers).
Otherwise, I use my automated tests at
https://github.com/inside-openflow/faucet-vagrant-tests using vagrant to
test different installation instructions that I reference, or plan on
referencing, in my articles. I don't expect those to pass all the time. I
just use them to give me a hint when something might be wrong and I can run
the tests manually.
Sorry for short response, on US central time and already left work and not
at my workstation. Hope the information helps.
-Leo
On Wed, Aug 31, 2016 at 5:49 PM Shivaram Mysore<EMAIL_ADDRESS>wrote:

Hi Leo,
(included<EMAIL_ADDRESS>mailing list as others may also be
interested)
One of our colleagues had a similar problem, when he did not follow Brad's
excellent instructions.
Can you please confirm if you  did:
docker build -t reannz/faucet-tests -f Dockerfile.tests .
apparmor_parser -R /etc/apparmor.d/usr.sbin.tcpdump
modprobe openvswitch
sudo docker run --privileged -ti reannz/faucet-tests
thanks
On Wed, Aug 31, 2016 at 11:14 AM, Leo Scott<EMAIL_ADDRESS>wrote:

I ran the Docker instance directly on my workstation (rather than in a
VM) and I get the same freeze as before. I pressed Ctrl+C after half an
hour. This seems to be a new issue. Should I write a new ticket then?
full logs:
docker-build-20160831.txt
https://github.com/onfsdn/faucet/files/447971/docker-build-20160831.txt
docker-run-20160831.txt
https://github.com/onfsdn/faucet/files/447972/docker-run-20160831.txt
excerpt:
*** Ping: testing ping reachability
u8c1 -> u8c2 u8c3 u8c4
u8c2 -> u8c1 u8c3 u8c4
u8c3 -> u8c1 u8c2 u8c4
u8c4 -> u8c1 u8c2 u8c3
*** Results: 0% dropped (12/12 received)
..^CTraceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/concurrencytest.py", line 82, in do_fork
process_suite.run(subunit_result)
File "/usr/lib/python2.7/unittest/suite.py", line 108, in run
test(result)
File "/usr/lib/python2.7/unittest/case.py", line 393, in call
return self.run(*args, **kwds)
File "/usr/lib/python2.7/unittest/case.py", line 320, in run
self.setUp()
File "./faucet_mininet_test.py", line 1197, in setUp
self.start_net()
File "./faucet_mininet_test.py", line 305, in start_net
self.net.waitConnected()
File "build/bdist.linux-x86_64/egg/mininet/net.py", line 185, in waitConnected
if switch.connected():
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 1118, in connected
uuid, 'is_connected' ):
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 1081, in vsctl
return self.cmd( 'ovs-vsctl', *args, **kwargs )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 351, in cmd
return self.waitOutput( verbose )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 338, in waitOutput
data = self.monitor( findPid=findPid )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 305, in monitor
data = self.read( 1024 )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 217, in read
data = os.read( self.stdout.fileno(), maxbytes - count )
KeyboardInterrupt
ETraceback (most recent call last):
File "./faucet_mininet_test.py", line 1882, in
run_tests()
File "./faucet_mininet_test.py", line 1858, in run_tests
results.append(parallel_runner.run(parallel_suite))
File "/usr/lib/python2.7/unittest/runner.py", line 151, in run
test(result)
File "/usr/local/lib/python2.7/dist-packages/unittest2/suite.py", line 87, in call
return self.run(*args, **kwds)
File "/usr/local/lib/python2.7/dist-packages/testtools/testsuite.py", line 95, in run
finished_test = queue.get()
File "/usr/lib/python2.7/Queue.py", line 168, in get
self.not_empty.wait()
File "/usr/lib/python2.7/threading.py", line 340, in wait
waiter.acquire()
KeyboardInterrupt
real    31m2.707s
user    6m20.525s
sys     0m58.517s
Container built with --no-cache to ensure the most up-to-date build.
Workstation has 32GB RAM and 8 (real) cores, so I doubt resources were an
issue.
—
You are receiving this because you commented.

Reply to this email directly, view it on GitHub
https://github.com/onfsdn/faucet/issues/10#issuecomment-243852272, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABmf8609c-gZ4izyBcBz0mSbb2fIhc6cks5qlcR8gaJpZM4Jmr2l
.

--
Latest info about Ryu Faucet is available @
http://onfsdn.github.io/faucet/
You received this message because you are subscribed to the Google Groups
"Faucet Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to<EMAIL_ADDRESS>To post to this group, send email to<EMAIL_ADDRESS>To view this discussion on the web visit
https://groups.google.com/a/openflowsdn.org/d/msgid/faucet-dev/CAJRY%2BjqE7a-J%3D4ixG39qNNB8tZWFuGO6gk6gzMEgsiMjKRcHJQ%40mail.gmail.com
https://groups.google.com/a/openflowsdn.org/d/msgid/faucet-dev/CAJRY%2BjqE7a-J%3D4ixG39qNNB8tZWFuGO6gk6gzMEgsiMjKRcHJQ%40mail.gmail.com?utm_medium=email&utm_source=footer
.

Thanks! I'll take a look for differences. On my box here the provided
instructions work (always the way isn't it :-).
I'm on for reference:
Description: Ubuntu 16.04.1 LTS
faucet@faucet:~/faucet$ uname -a
Linux  faucet 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
On Thu, Sep 1, 2016 at 10:51 AM, Leo Scott<EMAIL_ADDRESS>wrote:

Had just finished my draft to Josh before you sent this. Here it is for
the mailing list (short answer: yes, on two platforms).
Tests fail when following the README.docker.md instructions. Docker image
in privilege mode, with tcpdump apparmor profile removed and openvswitch
module loaded before running. Image built with --no-cache to ensure prior
builds did not affect test.
You can see my complete build and run console log (including commands) in
https://github.com/onfsdn/faucet/issues/10, see my last comment. I am
performing the exact directions in the README.docker.md file (at least as
of this morning). The last comment demonstrates the same issue running the
docker image directly on my workstation (I usually use separate VM
workspaces for different projects, even when running Docker containers).
Otherwise, I use my automated tests at https://github.com/inside-
openflow/faucet-vagrant-tests using vagrant to test different
installation instructions that I reference, or plan on referencing, in my
articles. I don't expect those to pass all the time. I just use them to
give me a hint when something might be wrong and I can run the tests
manually.
Sorry for short response, on US central time and already left work and not
at my workstation. Hope the information helps.
-Leo
On Wed, Aug 31, 2016 at 5:49 PM Shivaram Mysore<EMAIL_ADDRESS>wrote:

Hi Leo,
(included<EMAIL_ADDRESS>mailing list as others may also be
interested)
One of our colleagues had a similar problem, when he did not follow
Brad's excellent instructions.
Can you please confirm if you  did:
docker build -t reannz/faucet-tests -f Dockerfile.tests .
apparmor_parser -R /etc/apparmor.d/usr.sbin.tcpdump
modprobe openvswitch
sudo docker run --privileged -ti reannz/faucet-tests
thanks
On Wed, Aug 31, 2016 at 11:14 AM, Leo Scott<EMAIL_ADDRESS>wrote:

I ran the Docker instance directly on my workstation (rather than in a
VM) and I get the same freeze as before. I pressed Ctrl+C after half an
hour. This seems to be a new issue. Should I write a new ticket then?
full logs:
docker-build-20160831.txt
https://github.com/onfsdn/faucet/files/447971/docker-build-20160831.txt
docker-run-20160831.txt
https://github.com/onfsdn/faucet/files/447972/docker-run-20160831.txt
excerpt:
*** Ping: testing ping reachability
u8c1 -> u8c2 u8c3 u8c4
u8c2 -> u8c1 u8c3 u8c4
u8c3 -> u8c1 u8c2 u8c4
u8c4 -> u8c1 u8c2 u8c3
*** Results: 0% dropped (12/12 received)
..^CTraceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/concurrencytest.py", line 82, in do_fork
process_suite.run(subunit_result)
File "/usr/lib/python2.7/unittest/suite.py", line 108, in run
test(result)
File "/usr/lib/python2.7/unittest/case.py", line 393, in call
return self.run(*args, **kwds)
File "/usr/lib/python2.7/unittest/case.py", line 320, in run
self.setUp()
File "./faucet_mininet_test.py", line 1197, in setUp
self.start_net()
File "./faucet_mininet_test.py", line 305, in start_net
self.net.waitConnected()
File "build/bdist.linux-x86_64/egg/mininet/net.py", line 185, in waitConnected
if switch.connected():
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 1118, in connected
uuid, 'is_connected' ):
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 1081, in vsctl
return self.cmd( 'ovs-vsctl', *args, **kwargs )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 351, in cmd
return self.waitOutput( verbose )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 338, in waitOutput
data = self.monitor( findPid=findPid )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 305, in monitor
data = self.read( 1024 )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 217, in read
data = os.read( self.stdout.fileno(), maxbytes - count )
KeyboardInterrupt
ETraceback (most recent call last):
File "./faucet_mininet_test.py", line 1882, in
run_tests()
File "./faucet_mininet_test.py", line 1858, in run_tests
results.append(parallel_runner.run(parallel_suite))
File "/usr/lib/python2.7/unittest/runner.py", line 151, in run
test(result)
File "/usr/local/lib/python2.7/dist-packages/unittest2/suite.py", line 87, in call
return self.run(*args, **kwds)
File "/usr/local/lib/python2.7/dist-packages/testtools/testsuite.py", line 95, in run
finished_test = queue.get()
File "/usr/lib/python2.7/Queue.py", line 168, in get
self.not_empty.wait()
File "/usr/lib/python2.7/threading.py", line 340, in wait
waiter.acquire()
KeyboardInterrupt
real    31m2.707s
user    6m20.525s
sys     0m58.517s
Container built with --no-cache to ensure the most up-to-date build.
Workstation has 32GB RAM and 8 (real) cores, so I doubt resources were an
issue.
—
You are receiving this because you commented.

Reply to this email directly, view it on GitHub
https://github.com/onfsdn/faucet/issues/10#issuecomment-243852272, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABmf8609c-gZ4izyBcBz0mSbb2fIhc6cks5qlcR8gaJpZM4Jmr2l
.

--
Latest info about Ryu Faucet is available @ http://onfsdn.github.io/
faucet/
You received this message because you are subscribed to the Google Groups
"Faucet Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to<EMAIL_ADDRESS>To post to this group, send email to<EMAIL_ADDRESS>To view this discussion on the web visit https://groups.google.com/a/
openflowsdn.org/d/msgid/faucet-dev/CAJRY%2BjqE7a-J%
3D4ixG39qNNB8tZWFuGO6gk6gzMEgsiMjKRcHJQ%40mail.gmail.com
https://groups.google.com/a/openflowsdn.org/d/msgid/faucet-dev/CAJRY%2BjqE7a-J%3D4ixG39qNNB8tZWFuGO6gk6gzMEgsiMjKRcHJQ%40mail.gmail.com?utm_medium=email&utm_source=footer
.

--
Latest info about Ryu Faucet is available @ http://onfsdn.github.io/
faucet/
You received this message because you are subscribed to the Google Groups
"Faucet Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to<EMAIL_ADDRESS>To post to this group, send email to<EMAIL_ADDRESS>To view this discussion on the web visit https://groups.google.com/a/
openflowsdn.org/d/msgid/faucet-dev/CAPVxS6GbBRYGR6KDF8EMVMfsV25im
Ud%2Bohhs5_Qpa2KG6WKFng%40mail.gmail.com
https://groups.google.com/a/openflowsdn.org/d/msgid/faucet-dev/CAPVxS6GbBRYGR6KDF8EMVMfsV25imUd%2Bohhs5_Qpa2KG6WKFng%40mail.gmail.com?utm_medium=email&utm_source=footer
.

Using 14.04 on workstation, 16.04 in workspace(VMware) and test(virtual
box) VMs. Only using one hypervisor at a time. HTH -Leo
On Wed, Aug 31, 2016, 18:18 Josh Bailey<EMAIL_ADDRESS>wrote:

Thanks! I'll take a look for differences. On my box here the provided
instructions work (always the way isn't it :-).
I'm on for reference:
Description: Ubuntu 16.04.1 LTS
faucet@faucet:~/faucet$ uname -a
Linux  faucet 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
On Thu, Sep 1, 2016 at 10:51 AM, Leo Scott<EMAIL_ADDRESS>wrote:

Had just finished my draft to Josh before you sent this. Here it is for
the mailing list (short answer: yes, on two platforms).
Tests fail when following the README.docker.md instructions. Docker
image in privilege mode, with tcpdump apparmor profile removed and
openvswitch module loaded before running. Image built with --no-cache to
ensure prior builds did not affect test.
You can see my complete build and run console log (including commands) in
https://github.com/onfsdn/faucet/issues/10, see my last comment. I am
performing the exact directions in the README.docker.md file (at least
as of this morning). The last comment demonstrates the same issue running
the docker image directly on my workstation (I usually use separate VM
workspaces for different projects, even when running Docker containers).
Otherwise, I use my automated tests at
https://github.com/inside-openflow/faucet-vagrant-tests using vagrant to
test different installation instructions that I reference, or plan on
referencing, in my articles. I don't expect those to pass all the time. I
just use them to give me a hint when something might be wrong and I can run
the tests manually.
Sorry for short response, on US central time and already left work and
not at my workstation. Hope the information helps.
-Leo
On Wed, Aug 31, 2016 at 5:49 PM Shivaram Mysore <
<EMAIL_ADDRESS>wrote:

Hi Leo,
(included<EMAIL_ADDRESS>mailing list as others may also be
interested)
One of our colleagues had a similar problem, when he did not follow
Brad's excellent instructions.
Can you please confirm if you  did:
docker build -t reannz/faucet-tests -f Dockerfile.tests .
apparmor_parser -R /etc/apparmor.d/usr.sbin.tcpdump
modprobe openvswitch
sudo docker run --privileged -ti reannz/faucet-tests
thanks
On Wed, Aug 31, 2016 at 11:14 AM, Leo Scott<EMAIL_ADDRESS>wrote:

I ran the Docker instance directly on my workstation (rather than in a
VM) and I get the same freeze as before. I pressed Ctrl+C after half an
hour. This seems to be a new issue. Should I write a new ticket then?
full logs:
docker-build-20160831.txt
https://github.com/onfsdn/faucet/files/447971/docker-build-20160831.txt
docker-run-20160831.txt
https://github.com/onfsdn/faucet/files/447972/docker-run-20160831.txt
excerpt:
*** Ping: testing ping reachability
u8c1 -> u8c2 u8c3 u8c4
u8c2 -> u8c1 u8c3 u8c4
u8c3 -> u8c1 u8c2 u8c4
u8c4 -> u8c1 u8c2 u8c3
*** Results: 0% dropped (12/12 received)
..^CTraceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/concurrencytest.py", line 82, in do_fork
process_suite.run(subunit_result)
File "/usr/lib/python2.7/unittest/suite.py", line 108, in run
test(result)
File "/usr/lib/python2.7/unittest/case.py", line 393, in call
return self.run(*args, **kwds)
File "/usr/lib/python2.7/unittest/case.py", line 320, in run
self.setUp()
File "./faucet_mininet_test.py", line 1197, in setUp
self.start_net()
File "./faucet_mininet_test.py", line 305, in start_net
self.net.waitConnected()
File "build/bdist.linux-x86_64/egg/mininet/net.py", line 185, in waitConnected
if switch.connected():
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 1118, in connected
uuid, 'is_connected' ):
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 1081, in vsctl
return self.cmd( 'ovs-vsctl', *args, **kwargs )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 351, in cmd
return self.waitOutput( verbose )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 338, in waitOutput
data = self.monitor( findPid=findPid )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 305, in monitor
data = self.read( 1024 )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 217, in read
data = os.read( self.stdout.fileno(), maxbytes - count )
KeyboardInterrupt
ETraceback (most recent call last):
File "./faucet_mininet_test.py", line 1882, in
run_tests()
File "./faucet_mininet_test.py", line 1858, in run_tests
results.append(parallel_runner.run(parallel_suite))
File "/usr/lib/python2.7/unittest/runner.py", line 151, in run
test(result)
File "/usr/local/lib/python2.7/dist-packages/unittest2/suite.py", line 87, in call
return self.run(*args, **kwds)
File "/usr/local/lib/python2.7/dist-packages/testtools/testsuite.py", line 95, in run
finished_test = queue.get()
File "/usr/lib/python2.7/Queue.py", line 168, in get
self.not_empty.wait()
File "/usr/lib/python2.7/threading.py", line 340, in wait
waiter.acquire()
KeyboardInterrupt
real    31m2.707s
user    6m20.525s
sys     0m58.517s
Container built with --no-cache to ensure the most up-to-date build.
Workstation has 32GB RAM and 8 (real) cores, so I doubt resources were an
issue.
—
You are receiving this because you commented.

Reply to this email directly, view it on GitHub
https://github.com/onfsdn/faucet/issues/10#issuecomment-243852272,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABmf8609c-gZ4izyBcBz0mSbb2fIhc6cks5qlcR8gaJpZM4Jmr2l
.

--
Latest info about Ryu Faucet is available @
http://onfsdn.github.io/faucet/
You received this message because you are subscribed to the Google
Groups "Faucet Dev" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to<EMAIL_ADDRESS>To post to this group, send email to<EMAIL_ADDRESS>To view this discussion on the web visit
https://groups.google.com/a/openflowsdn.org/d/msgid/faucet-dev/CAJRY%2BjqE7a-J%3D4ixG39qNNB8tZWFuGO6gk6gzMEgsiMjKRcHJQ%40mail.gmail.com
https://groups.google.com/a/openflowsdn.org/d/msgid/faucet-dev/CAJRY%2BjqE7a-J%3D4ixG39qNNB8tZWFuGO6gk6gzMEgsiMjKRcHJQ%40mail.gmail.com?utm_medium=email&utm_source=footer
.

--
Latest info about Ryu Faucet is available @
http://onfsdn.github.io/faucet/
You received this message because you are subscribed to the Google Groups
"Faucet Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to<EMAIL_ADDRESS>To post to this group, send email to<EMAIL_ADDRESS>
To view this discussion on the web visit

https://groups.google.com/a/openflowsdn.org/d/msgid/faucet-dev/CAPVxS6GbBRYGR6KDF8EMVMfsV25imUd%2Bohhs5_Qpa2KG6WKFng%40mail.gmail.com
https://groups.google.com/a/openflowsdn.org/d/msgid/faucet-dev/CAPVxS6GbBRYGR6KDF8EMVMfsV25imUd%2Bohhs5_Qpa2KG6WKFng%40mail.gmail.com?utm_medium=email&utm_source=footer
.

Ah! Sorry I didn't understand that it hard partially been able to run (as
opposed not starting at all). I have had problems with namespace resource
leaks in the past. Can you let me know:

What kernel you're on (I'll use the same to compare).
Is it possible to start the container and then run the test script
manually, interrupt it when it gets stuck, and then take a look within the
environment (eg test logs in /tmp/)? You can also also remove the
shutil.rmtree() to leave logs behind, in case it's one test that's flakey -
that'll keep the diagnostic information around.

Thanks for your patience, and sorry for the trouble!
On Thu, Sep 1, 2016 at 11:18 AM, Josh Bailey<EMAIL_ADDRESS>wrote:

Thanks! I'll take a look for differences. On my box here the provided
instructions work (always the way isn't it :-).
I'm on for reference:
Description: Ubuntu 16.04.1 LTS
faucet@faucet:~/faucet$ uname -a
Linux  faucet 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
On Thu, Sep 1, 2016 at 10:51 AM, Leo Scott<EMAIL_ADDRESS>wrote:

Had just finished my draft to Josh before you sent this. Here it is for
the mailing list (short answer: yes, on two platforms).
Tests fail when following the README.docker.md instructions. Docker
image in privilege mode, with tcpdump apparmor profile removed and
openvswitch module loaded before running. Image built with --no-cache to
ensure prior builds did not affect test.
You can see my complete build and run console log (including commands) in
https://github.com/onfsdn/faucet/issues/10, see my last comment. I am
performing the exact directions in the README.docker.md file (at least
as of this morning). The last comment demonstrates the same issue running
the docker image directly on my workstation (I usually use separate VM
workspaces for different projects, even when running Docker containers).
Otherwise, I use my automated tests at https://github.com/inside-o
penflow/faucet-vagrant-tests using vagrant to test different
installation instructions that I reference, or plan on referencing, in my
articles. I don't expect those to pass all the time. I just use them to
give me a hint when something might be wrong and I can run the tests
manually.
Sorry for short response, on US central time and already left work and
not at my workstation. Hope the information helps.
-Leo
On Wed, Aug 31, 2016 at 5:49 PM Shivaram Mysore <
<EMAIL_ADDRESS>wrote:

Hi Leo,
(included<EMAIL_ADDRESS>mailing list as others may also be
interested)
One of our colleagues had a similar problem, when he did not follow
Brad's excellent instructions.
Can you please confirm if you  did:
docker build -t reannz/faucet-tests -f Dockerfile.tests .
apparmor_parser -R /etc/apparmor.d/usr.sbin.tcpdump
modprobe openvswitch
sudo docker run --privileged -ti reannz/faucet-tests
thanks
On Wed, Aug 31, 2016 at 11:14 AM, Leo Scott<EMAIL_ADDRESS>wrote:

I ran the Docker instance directly on my workstation (rather than in a
VM) and I get the same freeze as before. I pressed Ctrl+C after half an
hour. This seems to be a new issue. Should I write a new ticket then?
full logs:
docker-build-20160831.txt
https://github.com/onfsdn/faucet/files/447971/docker-build-20160831.txt
docker-run-20160831.txt
https://github.com/onfsdn/faucet/files/447972/docker-run-20160831.txt
excerpt:
*** Ping: testing ping reachability
u8c1 -> u8c2 u8c3 u8c4
u8c2 -> u8c1 u8c3 u8c4
u8c3 -> u8c1 u8c2 u8c4
u8c4 -> u8c1 u8c2 u8c3
*** Results: 0% dropped (12/12 received)
..^CTraceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/concurrencytest.py", line 82, in do_fork
process_suite.run(subunit_result)
File "/usr/lib/python2.7/unittest/suite.py", line 108, in run
test(result)
File "/usr/lib/python2.7/unittest/case.py", line 393, in call
return self.run(*args, **kwds)
File "/usr/lib/python2.7/unittest/case.py", line 320, in run
self.setUp()
File "./faucet_mininet_test.py", line 1197, in setUp
self.start_net()
File "./faucet_mininet_test.py", line 305, in start_net
self.net.waitConnected()
File "build/bdist.linux-x86_64/egg/mininet/net.py", line 185, in waitConnected
if switch.connected():
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 1118, in connected
uuid, 'is_connected' ):
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 1081, in vsctl
return self.cmd( 'ovs-vsctl', *args, **kwargs )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 351, in cmd
return self.waitOutput( verbose )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 338, in waitOutput
data = self.monitor( findPid=findPid )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 305, in monitor
data = self.read( 1024 )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 217, in read
data = os.read( self.stdout.fileno(), maxbytes - count )
KeyboardInterrupt
ETraceback (most recent call last):
File "./faucet_mininet_test.py", line 1882, in
run_tests()
File "./faucet_mininet_test.py", line 1858, in run_tests
results.append(parallel_runner.run(parallel_suite))
File "/usr/lib/python2.7/unittest/runner.py", line 151, in run
test(result)
File "/usr/local/lib/python2.7/dist-packages/unittest2/suite.py", line 87, in call
return self.run(*args, **kwds)
File "/usr/local/lib/python2.7/dist-packages/testtools/testsuite.py", line 95, in run
finished_test = queue.get()
File "/usr/lib/python2.7/Queue.py", line 168, in get
self.not_empty.wait()
File "/usr/lib/python2.7/threading.py", line 340, in wait
waiter.acquire()
KeyboardInterrupt
real    31m2.707s
user    6m20.525s
sys     0m58.517s
Container built with --no-cache to ensure the most up-to-date build.
Workstation has 32GB RAM and 8 (real) cores, so I doubt resources were an
issue.
—
You are receiving this because you commented.

Reply to this email directly, view it on GitHub
https://github.com/onfsdn/faucet/issues/10#issuecomment-243852272,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABmf8609c-gZ4izyBcBz0mSbb2fIhc6cks5qlcR8gaJpZM4Jmr2l
.

--
Latest info about Ryu Faucet is available @
http://onfsdn.github.io/faucet/
You received this message because you are subscribed to the Google
Groups "Faucet Dev" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to<EMAIL_ADDRESS>To post to this group, send email to<EMAIL_ADDRESS>To view this discussion on the web visit https://groups.google.com/a/op
enflowsdn.org/d/msgid/faucet-dev/CAJRY%2BjqE7a-J%3D4ixG39qN
NB8tZWFuGO6gk6gzMEgsiMjKRcHJQ%40mail.gmail.com
https://groups.google.com/a/openflowsdn.org/d/msgid/faucet-dev/CAJRY%2BjqE7a-J%3D4ixG39qNNB8tZWFuGO6gk6gzMEgsiMjKRcHJQ%40mail.gmail.com?utm_medium=email&utm_source=footer
.

--
Latest info about Ryu Faucet is available @
http://onfsdn.github.io/faucet/
You received this message because you are subscribed to the Google Groups
"Faucet Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to<EMAIL_ADDRESS>To post to this group, send email to<EMAIL_ADDRESS>To view this discussion on the web visit https://groups.google.com/a/op
enflowsdn.org/d/msgid/faucet-dev/CAPVxS6GbBRYGR6KDF8EMVMfsV
25imUd%2Bohhs5_Qpa2KG6WKFng%40mail.gmail.com
https://groups.google.com/a/openflowsdn.org/d/msgid/faucet-dev/CAPVxS6GbBRYGR6KDF8EMVMfsV25imUd%2Bohhs5_Qpa2KG6WKFng%40mail.gmail.com?utm_medium=email&utm_source=footer
.

Thanks - I am thinking the most likely explanation is a namespace resource
leak; please let me know what kernel you have and I'll try it.
On Thu, Sep 1, 2016 at 11:24 AM, Leo Scott<EMAIL_ADDRESS>wrote:

Using 14.04 on workstation, 16.04 in workspace(VMware) and test(virtual
box) VMs. Only using one hypervisor at a time. HTH -Leo
On Wed, Aug 31, 2016, 18:18 Josh Bailey<EMAIL_ADDRESS>wrote:

Thanks! I'll take a look for differences. On my box here the provided
instructions work (always the way isn't it :-).
I'm on for reference:
Description: Ubuntu 16.04.1 LTS
faucet@faucet:~/faucet$ uname -a
Linux  faucet 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC
2016 x86_64 x86_64 x86_64 GNU/Linux
On Thu, Sep 1, 2016 at 10:51 AM, Leo Scott<EMAIL_ADDRESS>wrote:

Had just finished my draft to Josh before you sent this. Here it is for
the mailing list (short answer: yes, on two platforms).
Tests fail when following the README.docker.md instructions. Docker
image in privilege mode, with tcpdump apparmor profile removed and
openvswitch module loaded before running. Image built with --no-cache to
ensure prior builds did not affect test.
You can see my complete build and run console log (including commands)
in https://github.com/onfsdn/faucet/issues/10, see my last comment. I
am performing the exact directions in the README.docker.md file (at
least as of this morning). The last comment demonstrates the same issue
running the docker image directly on my workstation (I usually use separate
VM workspaces for different projects, even when running Docker containers).
Otherwise, I use my automated tests at https://github.com/inside-
openflow/faucet-vagrant-tests using vagrant to test different
installation instructions that I reference, or plan on referencing, in my
articles. I don't expect those to pass all the time. I just use them to
give me a hint when something might be wrong and I can run the tests
manually.
Sorry for short response, on US central time and already left work and
not at my workstation. Hope the information helps.
-Leo
On Wed, Aug 31, 2016 at 5:49 PM Shivaram Mysore <
<EMAIL_ADDRESS>wrote:

Hi Leo,
(included<EMAIL_ADDRESS>mailing list as others may also
be interested)
One of our colleagues had a similar problem, when he did not follow
Brad's excellent instructions.
Can you please confirm if you  did:
docker build -t reannz/faucet-tests -f Dockerfile.tests .
apparmor_parser -R /etc/apparmor.d/usr.sbin.tcpdump
modprobe openvswitch
sudo docker run --privileged -ti reannz/faucet-tests
thanks
On Wed, Aug 31, 2016 at 11:14 AM, Leo Scott<EMAIL_ADDRESS>wrote:

I ran the Docker instance directly on my workstation (rather than in a
VM) and I get the same freeze as before. I pressed Ctrl+C after half an
hour. This seems to be a new issue. Should I write a new ticket then?
full logs:
docker-build-20160831.txt
https://github.com/onfsdn/faucet/files/447971/docker-build-20160831.txt
docker-run-20160831.txt
https://github.com/onfsdn/faucet/files/447972/docker-run-20160831.txt
excerpt:
*** Ping: testing ping reachability
u8c1 -> u8c2 u8c3 u8c4
u8c2 -> u8c1 u8c3 u8c4
u8c3 -> u8c1 u8c2 u8c4
u8c4 -> u8c1 u8c2 u8c3
*** Results: 0% dropped (12/12 received)
..^CTraceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/concurrencytest.py", line 82, in do_fork
process_suite.run(subunit_result)
File "/usr/lib/python2.7/unittest/suite.py", line 108, in run
test(result)
File "/usr/lib/python2.7/unittest/case.py", line 393, in call
return self.run(*args, **kwds)
File "/usr/lib/python2.7/unittest/case.py", line 320, in run
self.setUp()
File "./faucet_mininet_test.py", line 1197, in setUp
self.start_net()
File "./faucet_mininet_test.py", line 305, in start_net
self.net.waitConnected()
File "build/bdist.linux-x86_64/egg/mininet/net.py", line 185, in waitConnected
if switch.connected():
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 1118, in connected
uuid, 'is_connected' ):
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 1081, in vsctl
return self.cmd( 'ovs-vsctl', *args, **kwargs )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 351, in cmd
return self.waitOutput( verbose )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 338, in waitOutput
data = self.monitor( findPid=findPid )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 305, in monitor
data = self.read( 1024 )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 217, in read
data = os.read( self.stdout.fileno(), maxbytes - count )
KeyboardInterrupt
ETraceback (most recent call last):
File "./faucet_mininet_test.py", line 1882, in
run_tests()
File "./faucet_mininet_test.py", line 1858, in run_tests
results.append(parallel_runner.run(parallel_suite))
File "/usr/lib/python2.7/unittest/runner.py", line 151, in run
test(result)
File "/usr/local/lib/python2.7/dist-packages/unittest2/suite.py", line 87, in call
return self.run(*args, **kwds)
File "/usr/local/lib/python2.7/dist-packages/testtools/testsuite.py", line 95, in run
finished_test = queue.get()
File "/usr/lib/python2.7/Queue.py", line 168, in get
self.not_empty.wait()
File "/usr/lib/python2.7/threading.py", line 340, in wait
waiter.acquire()
KeyboardInterrupt
real    31m2.707s
user    6m20.525s
sys     0m58.517s
Container built with --no-cache to ensure the most up-to-date build.
Workstation has 32GB RAM and 8 (real) cores, so I doubt resources were an
issue.
—
You are receiving this because you commented.

Reply to this email directly, view it on GitHub
https://github.com/onfsdn/faucet/issues/10#issuecomment-243852272,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABmf8609c-gZ4izyBcBz0mSbb2fIhc6cks5qlcR8gaJpZM4Jmr2l
.

--
Latest info about Ryu Faucet is available @ http://onfsdn.github.io/
faucet/
You received this message because you are subscribed to the Google
Groups "Faucet Dev" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to<EMAIL_ADDRESS>To post to this group, send email to<EMAIL_ADDRESS>To view this discussion on the web visit https://groups.google.com/a/
openflowsdn.org/d/msgid/faucet-dev/CAJRY%2BjqE7a-J%
3D4ixG39qNNB8tZWFuGO6gk6gzMEgsiMjKRcHJQ%40mail.gmail.com
https://groups.google.com/a/openflowsdn.org/d/msgid/faucet-dev/CAJRY%2BjqE7a-J%3D4ixG39qNNB8tZWFuGO6gk6gzMEgsiMjKRcHJQ%40mail.gmail.com?utm_medium=email&utm_source=footer
.

--
Latest info about Ryu Faucet is available @ http://onfsdn.github.io/
faucet/
You received this message because you are subscribed to the Google
Groups "Faucet Dev" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to<EMAIL_ADDRESS>To post to this group, send email to<EMAIL_ADDRESS>
To view this discussion on the web visit https://groups.google.com/a/

openflowsdn.org/d/msgid/faucet-dev/CAPVxS6GbBRYGR6KDF8EMVMfsV25im
Ud%2Bohhs5_Qpa2KG6WKFng%40mail.gmail.com
https://groups.google.com/a/openflowsdn.org/d/msgid/faucet-dev/CAPVxS6GbBRYGR6KDF8EMVMfsV25imUd%2Bohhs5_Qpa2KG6WKFng%40mail.gmail.com?utm_medium=email&utm_source=footer
.

--
Latest info about Ryu Faucet is available @ http://onfsdn.github.io/
faucet/

You received this message because you are subscribed to the Google Groups
"Faucet Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to<EMAIL_ADDRESS>To post to this group, send email to<EMAIL_ADDRESS>To view this discussion on the web visit https://groups.google.com/a/
openflowsdn.org/d/msgid/faucet-dev/CAPVxS6FNZCwRArz5fuNm9NH7OYsjj
aRD19wRaOTCypb6pY0KXg%40mail.gmail.com
https://groups.google.com/a/openflowsdn.org/d/msgid/faucet-dev/CAPVxS6FNZCwRArz5fuNm9NH7OYsjjaRD19wRaOTCypb6pY0KXg%40mail.gmail.com?utm_medium=email&utm_source=footer
.

By the way. If you don't mind I'm happy to ssh it and see if I can figure
it out for you. Let me know!
On Sep 1, 2016 11:26 AM, "Josh Bailey"<EMAIL_ADDRESS>wrote:

Thanks - I am thinking the most likely explanation is a namespace resource
leak; please let me know what kernel you have and I'll try it.
On Thu, Sep 1, 2016 at 11:24 AM, Leo Scott<EMAIL_ADDRESS>wrote:

Using 14.04 on workstation, 16.04 in workspace(VMware) and test(virtual
box) VMs. Only using one hypervisor at a time. HTH -Leo
On Wed, Aug 31, 2016, 18:18 Josh Bailey<EMAIL_ADDRESS>wrote:

Thanks! I'll take a look for differences. On my box here the provided
instructions work (always the way isn't it :-).
I'm on for reference:
Description: Ubuntu 16.04.1 LTS
faucet@faucet:~/faucet$ uname -a
Linux  faucet 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC
2016 x86_64 x86_64 x86_64 GNU/Linux
On Thu, Sep 1, 2016 at 10:51 AM, Leo Scott<EMAIL_ADDRESS>wrote:

Had just finished my draft to Josh before you sent this. Here it is for
the mailing list (short answer: yes, on two platforms).
Tests fail when following the README.docker.md instructions. Docker
image in privilege mode, with tcpdump apparmor profile removed and
openvswitch module loaded before running. Image built with --no-cache to
ensure prior builds did not affect test.
You can see my complete build and run console log (including commands)
in https://github.com/onfsdn/faucet/issues/10, see my last comment. I
am performing the exact directions in the README.docker.md file (at
least as of this morning). The last comment demonstrates the same issue
running the docker image directly on my workstation (I usually use separate
VM workspaces for different projects, even when running Docker containers).
Otherwise, I use my automated tests at https://github.com/inside-o
penflow/faucet-vagrant-tests using vagrant to test different
installation instructions that I reference, or plan on referencing, in my
articles. I don't expect those to pass all the time. I just use them to
give me a hint when something might be wrong and I can run the tests
manually.
Sorry for short response, on US central time and already left work and
not at my workstation. Hope the information helps.
-Leo
On Wed, Aug 31, 2016 at 5:49 PM Shivaram Mysore <
<EMAIL_ADDRESS>wrote:

Hi Leo,
(included<EMAIL_ADDRESS>mailing list as others may also
be interested)
One of our colleagues had a similar problem, when he did not follow
Brad's excellent instructions.
Can you please confirm if you  did:
docker build -t reannz/faucet-tests -f Dockerfile.tests .
apparmor_parser -R /etc/apparmor.d/usr.sbin.tcpdump
modprobe openvswitch
sudo docker run --privileged -ti reannz/faucet-tests
thanks
On Wed, Aug 31, 2016 at 11:14 AM, Leo Scott<EMAIL_ADDRESS>wrote:

I ran the Docker instance directly on my workstation (rather than in
a VM) and I get the same freeze as before. I pressed Ctrl+C after half an
hour. This seems to be a new issue. Should I write a new ticket then?
full logs:
docker-build-20160831.txt
https://github.com/onfsdn/faucet/files/447971/docker-build-20160831.txt
docker-run-20160831.txt
https://github.com/onfsdn/faucet/files/447972/docker-run-20160831.txt
excerpt:
*** Ping: testing ping reachability
u8c1 -> u8c2 u8c3 u8c4
u8c2 -> u8c1 u8c3 u8c4
u8c3 -> u8c1 u8c2 u8c4
u8c4 -> u8c1 u8c2 u8c3
*** Results: 0% dropped (12/12 received)
..^CTraceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/concurrencytest.py", line 82, in do_fork
process_suite.run(subunit_result)
File "/usr/lib/python2.7/unittest/suite.py", line 108, in run
test(result)
File "/usr/lib/python2.7/unittest/case.py", line 393, in call
return self.run(*args, **kwds)
File "/usr/lib/python2.7/unittest/case.py", line 320, in run
self.setUp()
File "./faucet_mininet_test.py", line 1197, in setUp
self.start_net()
File "./faucet_mininet_test.py", line 305, in start_net
self.net.waitConnected()
File "build/bdist.linux-x86_64/egg/mininet/net.py", line 185, in waitConnected
if switch.connected():
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 1118, in connected
uuid, 'is_connected' ):
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 1081, in vsctl
return self.cmd( 'ovs-vsctl', *args, **kwargs )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 351, in cmd
return self.waitOutput( verbose )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 338, in waitOutput
data = self.monitor( findPid=findPid )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 305, in monitor
data = self.read( 1024 )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 217, in read
data = os.read( self.stdout.fileno(), maxbytes - count )
KeyboardInterrupt
ETraceback (most recent call last):
File "./faucet_mininet_test.py", line 1882, in
run_tests()
File "./faucet_mininet_test.py", line 1858, in run_tests
results.append(parallel_runner.run(parallel_suite))
File "/usr/lib/python2.7/unittest/runner.py", line 151, in run
test(result)
File "/usr/local/lib/python2.7/dist-packages/unittest2/suite.py", line 87, in call
return self.run(*args, **kwds)
File "/usr/local/lib/python2.7/dist-packages/testtools/testsuite.py", line 95, in run
finished_test = queue.get()
File "/usr/lib/python2.7/Queue.py", line 168, in get
self.not_empty.wait()
File "/usr/lib/python2.7/threading.py", line 340, in wait
waiter.acquire()
KeyboardInterrupt
real    31m2.707s
user    6m20.525s
sys     0m58.517s
Container built with --no-cache to ensure the most up-to-date build.
Workstation has 32GB RAM and 8 (real) cores, so I doubt resources were an
issue.
—
You are receiving this because you commented.

Reply to this email directly, view it on GitHub
https://github.com/onfsdn/faucet/issues/10#issuecomment-243852272,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABmf8609c-gZ4izyBcBz0mSbb2fIhc6cks5qlcR8gaJpZM4Jmr2l
.

--
Latest info about Ryu Faucet is available @
http://onfsdn.github.io/faucet/
You received this message because you are subscribed to the Google
Groups "Faucet Dev" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to<EMAIL_ADDRESS>To post to this group, send email to<EMAIL_ADDRESS>To view this discussion on the web visit
https://groups.google.com/a/openflowsdn.org/d/msgid/faucet-
dev/CAJRY%2BjqE7a-J%3D4ixG39qNNB8tZWFuGO6gk6gzMEgsiMjKRcHJQ%
40mail.gmail.com
https://groups.google.com/a/openflowsdn.org/d/msgid/faucet-dev/CAJRY%2BjqE7a-J%3D4ixG39qNNB8tZWFuGO6gk6gzMEgsiMjKRcHJQ%40mail.gmail.com?utm_medium=email&utm_source=footer
.

--
Latest info about Ryu Faucet is available @
http://onfsdn.github.io/faucet/
You received this message because you are subscribed to the Google
Groups "Faucet Dev" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to<EMAIL_ADDRESS>To post to this group, send email to<EMAIL_ADDRESS>
To view this discussion on the web visit https://groups.google.com/a/op

enflowsdn.org/d/msgid/faucet-dev/CAPVxS6GbBRYGR6KDF8EMVMfsV
25imUd%2Bohhs5_Qpa2KG6WKFng%40mail.gmail.com
https://groups.google.com/a/openflowsdn.org/d/msgid/faucet-dev/CAPVxS6GbBRYGR6KDF8EMVMfsV25imUd%2Bohhs5_Qpa2KG6WKFng%40mail.gmail.com?utm_medium=email&utm_source=footer
.

--
Latest info about Ryu Faucet is available @
http://onfsdn.github.io/faucet/

You received this message because you are subscribed to the Google Groups
"Faucet Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to<EMAIL_ADDRESS>To post to this group, send email to<EMAIL_ADDRESS>To view this discussion on the web visit https://groups.google.com/a/op
enflowsdn.org/d/msgid/faucet-dev/CAPVxS6FNZCwRArz5fuNm9NH7O
YsjjaRD19wRaOTCypb6pY0KXg%40mail.gmail.com
https://groups.google.com/a/openflowsdn.org/d/msgid/faucet-dev/CAPVxS6FNZCwRArz5fuNm9NH7OYsjjaRD19wRaOTCypb6pY0KXg%40mail.gmail.com?utm_medium=email&utm_source=footer
.

Just logged in to my workstation to get you kernel info:
Linux [redacted] 3.13.0-95-generic #142-Ubuntu SMP Fri Aug 12 17:00:09 UTC
2016 x86_64 x86_64 x86_64 GNU/Linux
Test VM kernel info:
Linux ubuntu-xenial 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:01:55 UTC
2016 x86_64 x86_64 x86_64 GNU/Linux
As far as SSH in to the workstation, I'm afraid I'm not set up to allow
that on my workstation, but I can set up some port forwarding so you can
log in to a test VM. I'll have to do that tomorrow, though. Please send me
your public SSH identity that you will use (privately if you wish) and I
can set that up tomorrow. I'll send login details privately.
I'm also willing to do a Hangouts session and share my screen so you can
see what I do. I'm on US Central time (GMT-0500 currently) and available
between 11:00 and 17:00 tomorrow, though I can schedule time outside that
range if needed.
Thanks for the help =)
-Leo
On Wed, Aug 31, 2016 at 6:26 PM Josh Bailey<EMAIL_ADDRESS>wrote:

Thanks - I am thinking the most likely explanation is a namespace resource
leak; please let me know what kernel you have and I'll try it.
On Thu, Sep 1, 2016 at 11:24 AM, Leo Scott<EMAIL_ADDRESS>wrote:

Using 14.04 on workstation, 16.04 in workspace(VMware) and test(virtual
box) VMs. Only using one hypervisor at a time. HTH -Leo
On Wed, Aug 31, 2016, 18:18 Josh Bailey<EMAIL_ADDRESS>wrote:

Thanks! I'll take a look for differences. On my box here the provided
instructions work (always the way isn't it :-).
I'm on for reference:
Description: Ubuntu 16.04.1 LTS
faucet@faucet:~/faucet$ uname -a
Linux  faucet 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC
2016 x86_64 x86_64 x86_64 GNU/Linux
On Thu, Sep 1, 2016 at 10:51 AM, Leo Scott<EMAIL_ADDRESS>wrote:

Had just finished my draft to Josh before you sent this. Here it is for
the mailing list (short answer: yes, on two platforms).
Tests fail when following the README.docker.md instructions. Docker
image in privilege mode, with tcpdump apparmor profile removed and
openvswitch module loaded before running. Image built with --no-cache to
ensure prior builds did not affect test.
You can see my complete build and run console log (including commands)
in https://github.com/onfsdn/faucet/issues/10, see my last comment. I
am performing the exact directions in the README.docker.md file (at
least as of this morning). The last comment demonstrates the same issue
running the docker image directly on my workstation (I usually use separate
VM workspaces for different projects, even when running Docker containers).
Otherwise, I use my automated tests at
https://github.com/inside-openflow/faucet-vagrant-tests using vagrant
to test different installation instructions that I reference, or plan on
referencing, in my articles. I don't expect those to pass all the time. I
just use them to give me a hint when something might be wrong and I can run
the tests manually.
Sorry for short response, on US central time and already left work and
not at my workstation. Hope the information helps.
-Leo
On Wed, Aug 31, 2016 at 5:49 PM Shivaram Mysore <
<EMAIL_ADDRESS>wrote:

Hi Leo,
(included<EMAIL_ADDRESS>mailing list as others may also
be interested)
One of our colleagues had a similar problem, when he did not follow
Brad's excellent instructions.
Can you please confirm if you  did:
docker build -t reannz/faucet-tests -f Dockerfile.tests .
apparmor_parser -R /etc/apparmor.d/usr.sbin.tcpdump
modprobe openvswitch
sudo docker run --privileged -ti reannz/faucet-tests
thanks
On Wed, Aug 31, 2016 at 11:14 AM, Leo Scott<EMAIL_ADDRESS>wrote:

I ran the Docker instance directly on my workstation (rather than in
a VM) and I get the same freeze as before. I pressed Ctrl+C after half an
hour. This seems to be a new issue. Should I write a new ticket then?
full logs:
docker-build-20160831.txt
https://github.com/onfsdn/faucet/files/447971/docker-build-20160831.txt
docker-run-20160831.txt
https://github.com/onfsdn/faucet/files/447972/docker-run-20160831.txt
excerpt:
*** Ping: testing ping reachability
u8c1 -> u8c2 u8c3 u8c4
u8c2 -> u8c1 u8c3 u8c4
u8c3 -> u8c1 u8c2 u8c4
u8c4 -> u8c1 u8c2 u8c3
*** Results: 0% dropped (12/12 received)
..^CTraceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/concurrencytest.py", line 82, in do_fork
process_suite.run(subunit_result)
File "/usr/lib/python2.7/unittest/suite.py", line 108, in run
test(result)
File "/usr/lib/python2.7/unittest/case.py", line 393, in call
return self.run(*args, **kwds)
File "/usr/lib/python2.7/unittest/case.py", line 320, in run
self.setUp()
File "./faucet_mininet_test.py", line 1197, in setUp
self.start_net()
File "./faucet_mininet_test.py", line 305, in start_net
self.net.waitConnected()
File "build/bdist.linux-x86_64/egg/mininet/net.py", line 185, in waitConnected
if switch.connected():
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 1118, in connected
uuid, 'is_connected' ):
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 1081, in vsctl
return self.cmd( 'ovs-vsctl', *args, **kwargs )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 351, in cmd
return self.waitOutput( verbose )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 338, in waitOutput
data = self.monitor( findPid=findPid )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 305, in monitor
data = self.read( 1024 )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 217, in read
data = os.read( self.stdout.fileno(), maxbytes - count )
KeyboardInterrupt
ETraceback (most recent call last):
File "./faucet_mininet_test.py", line 1882, in
run_tests()
File "./faucet_mininet_test.py", line 1858, in run_tests
results.append(parallel_runner.run(parallel_suite))
File "/usr/lib/python2.7/unittest/runner.py", line 151, in run
test(result)
File "/usr/local/lib/python2.7/dist-packages/unittest2/suite.py", line 87, in call
return self.run(*args, **kwds)
File "/usr/local/lib/python2.7/dist-packages/testtools/testsuite.py", line 95, in run
finished_test = queue.get()
File "/usr/lib/python2.7/Queue.py", line 168, in get
self.not_empty.wait()
File "/usr/lib/python2.7/threading.py", line 340, in wait
waiter.acquire()
KeyboardInterrupt
real    31m2.707s
user    6m20.525s
sys     0m58.517s
Container built with --no-cache to ensure the most up-to-date build.
Workstation has 32GB RAM and 8 (real) cores, so I doubt resources were an
issue.
—
You are receiving this because you commented.

Reply to this email directly, view it on GitHub
https://github.com/onfsdn/faucet/issues/10#issuecomment-243852272,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABmf8609c-gZ4izyBcBz0mSbb2fIhc6cks5qlcR8gaJpZM4Jmr2l
.

--
Latest info about Ryu Faucet is available @
http://onfsdn.github.io/faucet/
You received this message because you are subscribed to the Google
Groups "Faucet Dev" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to<EMAIL_ADDRESS>To post to this group, send email to<EMAIL_ADDRESS>To view this discussion on the web visit
https://groups.google.com/a/openflowsdn.org/d/msgid/faucet-dev/CAJRY%2BjqE7a-J%3D4ixG39qNNB8tZWFuGO6gk6gzMEgsiMjKRcHJQ%40mail.gmail.com
https://groups.google.com/a/openflowsdn.org/d/msgid/faucet-dev/CAJRY%2BjqE7a-J%3D4ixG39qNNB8tZWFuGO6gk6gzMEgsiMjKRcHJQ%40mail.gmail.com?utm_medium=email&utm_source=footer
.

--
Latest info about Ryu Faucet is available @
http://onfsdn.github.io/faucet/
You received this message because you are subscribed to the Google
Groups "Faucet Dev" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to<EMAIL_ADDRESS>To post to this group, send email to<EMAIL_ADDRESS>
To view this discussion on the web visit

https://groups.google.com/a/openflowsdn.org/d/msgid/faucet-dev/CAPVxS6GbBRYGR6KDF8EMVMfsV25imUd%2Bohhs5_Qpa2KG6WKFng%40mail.gmail.com
https://groups.google.com/a/openflowsdn.org/d/msgid/faucet-dev/CAPVxS6GbBRYGR6KDF8EMVMfsV25imUd%2Bohhs5_Qpa2KG6WKFng%40mail.gmail.com?utm_medium=email&utm_source=footer
.

--
Latest info about Ryu Faucet is available @
http://onfsdn.github.io/faucet/

You received this message because you are subscribed to the Google Groups
"Faucet Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to<EMAIL_ADDRESS>To post to this group, send email to<EMAIL_ADDRESS>
To view this discussion on the web visit

https://groups.google.com/a/openflowsdn.org/d/msgid/faucet-dev/CAPVxS6FNZCwRArz5fuNm9NH7OYsjjaRD19wRaOTCypb6pY0KXg%40mail.gmail.com
https://groups.google.com/a/openflowsdn.org/d/msgid/faucet-dev/CAPVxS6FNZCwRArz5fuNm9NH7OYsjjaRD19wRaOTCypb6pY0KXg%40mail.gmail.com?utm_medium=email&utm_source=footer
.

Thanks, will email key when back at desk.
One other question for the road; I'm using OVS 2.5.0. Can you confirm what
you have?
Thanks,
On Sep 1, 2016 11:47 AM, "Leo Scott"<EMAIL_ADDRESS>wrote:

Just logged in to my workstation to get you kernel info:
Linux [redacted] 3.13.0-95-generic #142-Ubuntu SMP Fri Aug 12 17:00:09 UTC
2016 x86_64 x86_64 x86_64 GNU/Linux
Test VM kernel info:
Linux ubuntu-xenial 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:01:55
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
As far as SSH in to the workstation, I'm afraid I'm not set up to allow
that on my workstation, but I can set up some port forwarding so you can
log in to a test VM. I'll have to do that tomorrow, though. Please send me
your public SSH identity that you will use (privately if you wish) and I
can set that up tomorrow. I'll send login details privately.
I'm also willing to do a Hangouts session and share my screen so you can
see what I do. I'm on US Central time (GMT-0500 currently) and available
between 11:00 and 17:00 tomorrow, though I can schedule time outside that
range if needed.
Thanks for the help =)
-Leo
On Wed, Aug 31, 2016 at 6:26 PM Josh Bailey<EMAIL_ADDRESS>wrote:

Thanks - I am thinking the most likely explanation is a namespace
resource leak; please let me know what kernel you have and I'll try it.
On Thu, Sep 1, 2016 at 11:24 AM, Leo Scott<EMAIL_ADDRESS>wrote:

Using 14.04 on workstation, 16.04 in workspace(VMware) and test(virtual
box) VMs. Only using one hypervisor at a time. HTH -Leo
On Wed, Aug 31, 2016, 18:18 Josh Bailey<EMAIL_ADDRESS>wrote:

Thanks! I'll take a look for differences. On my box here the provided
instructions work (always the way isn't it :-).
I'm on for reference:
Description: Ubuntu 16.04.1 LTS
faucet@faucet:~/faucet$ uname -a
Linux  faucet 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC
2016 x86_64 x86_64 x86_64 GNU/Linux
On Thu, Sep 1, 2016 at 10:51 AM, Leo Scott<EMAIL_ADDRESS>wrote:

Had just finished my draft to Josh before you sent this. Here it is
for the mailing list (short answer: yes, on two platforms).
Tests fail when following the README.docker.md instructions. Docker
image in privilege mode, with tcpdump apparmor profile removed and
openvswitch module loaded before running. Image built with --no-cache to
ensure prior builds did not affect test.
You can see my complete build and run console log (including commands)
in https://github.com/onfsdn/faucet/issues/10, see my last comment. I
am performing the exact directions in the README.docker.md file (at
least as of this morning). The last comment demonstrates the same issue
running the docker image directly on my workstation (I usually use separate
VM workspaces for different projects, even when running Docker containers).
Otherwise, I use my automated tests at https://github.com/inside-
openflow/faucet-vagrant-tests using vagrant to test different
installation instructions that I reference, or plan on referencing, in my
articles. I don't expect those to pass all the time. I just use them to
give me a hint when something might be wrong and I can run the tests
manually.
Sorry for short response, on US central time and already left work and
not at my workstation. Hope the information helps.
-Leo
On Wed, Aug 31, 2016 at 5:49 PM Shivaram Mysore <
<EMAIL_ADDRESS>wrote:

Hi Leo,
(included<EMAIL_ADDRESS>mailing list as others may also
be interested)
One of our colleagues had a similar problem, when he did not follow
Brad's excellent instructions.
Can you please confirm if you  did:
docker build -t reannz/faucet-tests -f Dockerfile.tests .
apparmor_parser -R /etc/apparmor.d/usr.sbin.tcpdump
modprobe openvswitch
sudo docker run --privileged -ti reannz/faucet-tests
thanks
On Wed, Aug 31, 2016 at 11:14 AM, Leo Scott<EMAIL_ADDRESS>
wrote:

I ran the Docker instance directly on my workstation (rather than in
a VM) and I get the same freeze as before. I pressed Ctrl+C after half an
hour. This seems to be a new issue. Should I write a new ticket then?
full logs:
docker-build-20160831.txt
https://github.com/onfsdn/faucet/files/447971/docker-build-20160831.txt
docker-run-20160831.txt
https://github.com/onfsdn/faucet/files/447972/docker-run-20160831.txt
excerpt:
*** Ping: testing ping reachability
u8c1 -> u8c2 u8c3 u8c4
u8c2 -> u8c1 u8c3 u8c4
u8c3 -> u8c1 u8c2 u8c4
u8c4 -> u8c1 u8c2 u8c3
*** Results: 0% dropped (12/12 received)
..^CTraceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/concurrencytest.py", line 82, in do_fork
process_suite.run(subunit_result)
File "/usr/lib/python2.7/unittest/suite.py", line 108, in run
test(result)
File "/usr/lib/python2.7/unittest/case.py", line 393, in call
return self.run(*args, **kwds)
File "/usr/lib/python2.7/unittest/case.py", line 320, in run
self.setUp()
File "./faucet_mininet_test.py", line 1197, in setUp
self.start_net()
File "./faucet_mininet_test.py", line 305, in start_net
self.net.waitConnected()
File "build/bdist.linux-x86_64/egg/mininet/net.py", line 185, in waitConnected
if switch.connected():
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 1118, in connected
uuid, 'is_connected' ):
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 1081, in vsctl
return self.cmd( 'ovs-vsctl', *args, **kwargs )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 351, in cmd
return self.waitOutput( verbose )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 338, in waitOutput
data = self.monitor( findPid=findPid )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 305, in monitor
data = self.read( 1024 )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 217, in read
data = os.read( self.stdout.fileno(), maxbytes - count )
KeyboardInterrupt
ETraceback (most recent call last):
File "./faucet_mininet_test.py", line 1882, in
run_tests()
File "./faucet_mininet_test.py", line 1858, in run_tests
results.append(parallel_runner.run(parallel_suite))
File "/usr/lib/python2.7/unittest/runner.py", line 151, in run
test(result)
File "/usr/local/lib/python2.7/dist-packages/unittest2/suite.py", line 87, in call
return self.run(*args, **kwds)
File "/usr/local/lib/python2.7/dist-packages/testtools/testsuite.py", line 95, in run
finished_test = queue.get()
File "/usr/lib/python2.7/Queue.py", line 168, in get
self.not_empty.wait()
File "/usr/lib/python2.7/threading.py", line 340, in wait
waiter.acquire()
KeyboardInterrupt
real    31m2.707s
user    6m20.525s
sys     0m58.517s
Container built with --no-cache to ensure the most up-to-date
build. Workstation has 32GB RAM and 8 (real) cores, so I doubt resources
were an issue.
—
You are receiving this because you commented.

Reply to this email directly, view it on GitHub
https://github.com/onfsdn/faucet/issues/10#issuecomment-243852272,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABmf8609c-gZ4izyBcBz0mSbb2fIhc6cks5qlcR8gaJpZM4Jmr2l
.

--
Latest info about Ryu Faucet is available @ http://onfsdn.github.io/
faucet/
You received this message because you are subscribed to the Google
Groups "Faucet Dev" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to<EMAIL_ADDRESS>To post to this group, send email to<EMAIL_ADDRESS>To view this discussion on the web visit https://groups.google.com/a/
openflowsdn.org/d/msgid/faucet-dev/CAJRY%2BjqE7a-J%
3D4ixG39qNNB8tZWFuGO6gk6gzMEgsiMjKRcHJQ%40mail.gmail.com
https://groups.google.com/a/openflowsdn.org/d/msgid/faucet-dev/CAJRY%2BjqE7a-J%3D4ixG39qNNB8tZWFuGO6gk6gzMEgsiMjKRcHJQ%40mail.gmail.com?utm_medium=email&utm_source=footer
.

--
Latest info about Ryu Faucet is available @ http://onfsdn.github.io/
faucet/
You received this message because you are subscribed to the Google
Groups "Faucet Dev" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to<EMAIL_ADDRESS>To post to this group, send email to<EMAIL_ADDRESS>
To view this discussion on the web visit https://groups.google.com/a/

openflowsdn.org/d/msgid/faucet-dev/CAPVxS6GbBRYGR6KDF8EMVMfsV25im
Ud%2Bohhs5_Qpa2KG6WKFng%40mail.gmail.com
https://groups.google.com/a/openflowsdn.org/d/msgid/faucet-dev/CAPVxS6GbBRYGR6KDF8EMVMfsV25imUd%2Bohhs5_Qpa2KG6WKFng%40mail.gmail.com?utm_medium=email&utm_source=footer
.

--
Latest info about Ryu Faucet is available @ http://onfsdn.github.io/
faucet/

You received this message because you are subscribed to the Google
Groups "Faucet Dev" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to<EMAIL_ADDRESS>To post to this group, send email to<EMAIL_ADDRESS>
To view this discussion on the web visit https://groups.google.com/a/

openflowsdn.org/d/msgid/faucet-dev/CAPVxS6FNZCwRArz5fuNm9NH7OYsjj
aRD19wRaOTCypb6pY0KXg%40mail.gmail.com
https://groups.google.com/a/openflowsdn.org/d/msgid/faucet-dev/CAPVxS6FNZCwRArz5fuNm9NH7OYsjjaRD19wRaOTCypb6pY0KXg%40mail.gmail.com?utm_medium=email&utm_source=footer
.

Ach, trying to do from phone. I see OVS 2.5. OK, next step is log in will
send key.
On Sep 1, 2016 11:54 AM, "Josh Bailey"<EMAIL_ADDRESS>wrote:

Thanks, will email key when back at desk.
One other question for the road; I'm using OVS 2.5.0. Can you confirm what
you have?
Thanks,
On Sep 1, 2016 11:47 AM, "Leo Scott"<EMAIL_ADDRESS>wrote:

Just logged in to my workstation to get you kernel info:
Linux [redacted] 3.13.0-95-generic #142-Ubuntu SMP Fri Aug 12 17:00:09
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Test VM kernel info:
Linux ubuntu-xenial 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:01:55
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
As far as SSH in to the workstation, I'm afraid I'm not set up to allow
that on my workstation, but I can set up some port forwarding so you can
log in to a test VM. I'll have to do that tomorrow, though. Please send me
your public SSH identity that you will use (privately if you wish) and I
can set that up tomorrow. I'll send login details privately.
I'm also willing to do a Hangouts session and share my screen so you can
see what I do. I'm on US Central time (GMT-0500 currently) and available
between 11:00 and 17:00 tomorrow, though I can schedule time outside that
range if needed.
Thanks for the help =)
-Leo
On Wed, Aug 31, 2016 at 6:26 PM Josh Bailey<EMAIL_ADDRESS>wrote:

Thanks - I am thinking the most likely explanation is a namespace
resource leak; please let me know what kernel you have and I'll try it.
On Thu, Sep 1, 2016 at 11:24 AM, Leo Scott<EMAIL_ADDRESS>wrote:

Using 14.04 on workstation, 16.04 in workspace(VMware) and test(virtual
box) VMs. Only using one hypervisor at a time. HTH -Leo
On Wed, Aug 31, 2016, 18:18 Josh Bailey<EMAIL_ADDRESS>wrote:

Thanks! I'll take a look for differences. On my box here the provided
instructions work (always the way isn't it :-).
I'm on for reference:
Description: Ubuntu 16.04.1 LTS
faucet@faucet:~/faucet$ uname -a
Linux  faucet 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC
2016 x86_64 x86_64 x86_64 GNU/Linux
On Thu, Sep 1, 2016 at 10:51 AM, Leo Scott<EMAIL_ADDRESS>wrote:

Had just finished my draft to Josh before you sent this. Here it is
for the mailing list (short answer: yes, on two platforms).
Tests fail when following the README.docker.md instructions. Docker
image in privilege mode, with tcpdump apparmor profile removed and
openvswitch module loaded before running. Image built with --no-cache to
ensure prior builds did not affect test.
You can see my complete build and run console log (including
commands) in https://github.com/onfsdn/faucet/issues/10, see my last
comment. I am performing the exact directions in the README.docker.md
file (at least as of this morning). The last comment demonstrates the same
issue running the docker image directly on my workstation (I usually use
separate VM workspaces for different projects, even when running Docker
containers).
Otherwise, I use my automated tests at https://github.com/inside-o
penflow/faucet-vagrant-tests using vagrant to test different
installation instructions that I reference, or plan on referencing, in my
articles. I don't expect those to pass all the time. I just use them to
give me a hint when something might be wrong and I can run the tests
manually.
Sorry for short response, on US central time and already left work
and not at my workstation. Hope the information helps.
-Leo
On Wed, Aug 31, 2016 at 5:49 PM Shivaram Mysore <
<EMAIL_ADDRESS>wrote:

Hi Leo,
(included<EMAIL_ADDRESS>mailing list as others may
also be interested)
One of our colleagues had a similar problem, when he did not follow
Brad's excellent instructions.
Can you please confirm if you  did:
docker build -t reannz/faucet-tests -f Dockerfile.tests .
apparmor_parser -R /etc/apparmor.d/usr.sbin.tcpdump
modprobe openvswitch
sudo docker run --privileged -ti reannz/faucet-tests
thanks
On Wed, Aug 31, 2016 at 11:14 AM, Leo Scott <
<EMAIL_ADDRESS>wrote:

I ran the Docker instance directly on my workstation (rather than
in a VM) and I get the same freeze as before. I pressed Ctrl+C after half
an hour. This seems to be a new issue. Should I write a new ticket then?
full logs:
docker-build-20160831.txt
https://github.com/onfsdn/faucet/files/447971/docker-build-20160831.txt
docker-run-20160831.txt
https://github.com/onfsdn/faucet/files/447972/docker-run-20160831.txt
excerpt:
*** Ping: testing ping reachability
u8c1 -> u8c2 u8c3 u8c4
u8c2 -> u8c1 u8c3 u8c4
u8c3 -> u8c1 u8c2 u8c4
u8c4 -> u8c1 u8c2 u8c3
*** Results: 0% dropped (12/12 received)
..^CTraceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/concurrencytest.py", line 82, in do_fork
process_suite.run(subunit_result)
File "/usr/lib/python2.7/unittest/suite.py", line 108, in run
test(result)
File "/usr/lib/python2.7/unittest/case.py", line 393, in call
return self.run(*args, **kwds)
File "/usr/lib/python2.7/unittest/case.py", line 320, in run
self.setUp()
File "./faucet_mininet_test.py", line 1197, in setUp
self.start_net()
File "./faucet_mininet_test.py", line 305, in start_net
self.net.waitConnected()
File "build/bdist.linux-x86_64/egg/mininet/net.py", line 185, in waitConnected
if switch.connected():
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 1118, in connected
uuid, 'is_connected' ):
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 1081, in vsctl
return self.cmd( 'ovs-vsctl', *args, **kwargs )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 351, in cmd
return self.waitOutput( verbose )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 338, in waitOutput
data = self.monitor( findPid=findPid )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 305, in monitor
data = self.read( 1024 )
File "build/bdist.linux-x86_64/egg/mininet/node.py", line 217, in read
data = os.read( self.stdout.fileno(), maxbytes - count )
KeyboardInterrupt
ETraceback (most recent call last):
File "./faucet_mininet_test.py", line 1882, in
run_tests()
File "./faucet_mininet_test.py", line 1858, in run_tests
results.append(parallel_runner.run(parallel_suite))
File "/usr/lib/python2.7/unittest/runner.py", line 151, in run
test(result)
File "/usr/local/lib/python2.7/dist-packages/unittest2/suite.py", line 87, in call
return self.run(*args, **kwds)
File "/usr/local/lib/python2.7/dist-packages/testtools/testsuite.py", line 95, in run
finished_test = queue.get()
File "/usr/lib/python2.7/Queue.py", line 168, in get
self.not_empty.wait()
File "/usr/lib/python2.7/threading.py", line 340, in wait
waiter.acquire()
KeyboardInterrupt
real    31m2.707s
user    6m20.525s
sys     0m58.517s
Container built with --no-cache to ensure the most up-to-date
build. Workstation has 32GB RAM and 8 (real) cores, so I doubt resources
were an issue.
—
You are receiving this because you commented.

Reply to this email directly, view it on GitHub
https://github.com/onfsdn/faucet/issues/10#issuecomment-243852272,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABmf8609c-gZ4izyBcBz0mSbb2fIhc6cks5qlcR8gaJpZM4Jmr2l
.

--
Latest info about Ryu Faucet is available @
http://onfsdn.github.io/faucet/
You received this message because you are subscribed to the Google
Groups "Faucet Dev" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to<EMAIL_ADDRESS>To post to this group, send email to<EMAIL_ADDRESS>To view this discussion on the web visit
https://groups.google.com/a/openflowsdn.org/d/msgid/faucet-
dev/CAJRY%2BjqE7a-J%3D4ixG39qNNB8tZWFuGO6gk6gzMEgsiMjKRcHJQ%
40mail.gmail.com
https://groups.google.com/a/openflowsdn.org/d/msgid/faucet-dev/CAJRY%2BjqE7a-J%3D4ixG39qNNB8tZWFuGO6gk6gzMEgsiMjKRcHJQ%40mail.gmail.com?utm_medium=email&utm_source=footer
.

--
Latest info about Ryu Faucet is available @
http://onfsdn.github.io/faucet/
You received this message because you are subscribed to the Google
Groups "Faucet Dev" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to<EMAIL_ADDRESS>To post to this group, send email to<EMAIL_ADDRESS>
To view this discussion on the web visit

https://groups.google.com/a/openflowsdn.org/d/msgid/faucet-
dev/CAPVxS6GbBRYGR6KDF8EMVMfsV25imUd%2Bohhs5_Qpa2KG6WKFng%40
mail.gmail.com
https://groups.google.com/a/openflowsdn.org/d/msgid/faucet-dev/CAPVxS6GbBRYGR6KDF8EMVMfsV25imUd%2Bohhs5_Qpa2KG6WKFng%40mail.gmail.com?utm_medium=email&utm_source=footer
.

--
Latest info about Ryu Faucet is available @
http://onfsdn.github.io/faucet/

You received this message because you are subscribed to the Google
Groups "Faucet Dev" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to<EMAIL_ADDRESS>To post to this group, send email to<EMAIL_ADDRESS>
To view this discussion on the web visit https://groups.google.com/a/op

enflowsdn.org/d/msgid/faucet-dev/CAPVxS6FNZCwRArz5fuNm9NH7O
YsjjaRD19wRaOTCypb6pY0KXg%40mail.gmail.com
https://groups.google.com/a/openflowsdn.org/d/msgid/faucet-dev/CAPVxS6FNZCwRArz5fuNm9NH7OYsjjaRD19wRaOTCypb6pY0KXg%40mail.gmail.com?utm_medium=email&utm_source=footer
.