Thangavelu K S | d4d954f | 2017-10-12 20:05:30 +0000 | [diff] [blame] | 1 | ubuntu@olt-tester:~/cord-tester/src/test/setup$ |
| 2 | ubuntu@olt-tester:~/cord-tester/src/test/setup$ ./voltha-test.py --test-type=dhcpl2relay:dhcpl2relay_exchange.test_dhcpl2relay_delete_and_add_sadis_app --manifest=manifest-olt-voltha-local.json --voltha-host=10.70.47.64 --olt-type=tibit-olt --olt-arg=00:0c:e2:31:05:00 --disable-cleanup --disable-teardown |
| 3 | Starting CordTester Web Server |
| 4 | * Running on http://127.0.0.1:5000/ (Press CTRL+C to quit) |
| 5 | * Restarting with stat |
| 6 | * Debugger is active! |
| 7 | * Debugger PIN: 718-316-938 |
| 8 | WARNING: No route found for IPv6 destination :: (no default route?) |
| 9 | Cleaning up existing cluster volumes |
| 10 | Onos IP 10.70.47.64 |
| 11 | Installing ONOS cord apps |
| 12 | # Host [10.70.47.64]:8101 found: line 5 |
| 13 | /root/.ssh/known_hosts updated. |
| 14 | Original contents retained as /root/.ssh/known_hosts.old |
| 15 | onoscli: eof exception found |
| 16 | onoscli: logout |
| 17 | |
| 18 | Connection to 10.70.47.64 closed. |
| 19 | |
| 20 | result.ok, result.status_code are False and 409 |
| 21 | ONOS app cord-config, version 3.0-SNAPSHOT installed |
| 22 | result.ok, result.status_code are False and 409 |
| 23 | ONOS app sadis-app, version 3.0-SNAPSHOT installed |
| 24 | result.ok, result.status_code are False and 409 |
| 25 | ONOS app olt-app, version 3.0-SNAPSHOT installed |
| 26 | result.ok, result.status_code are False and 409 |
| 27 | ONOS app aaa, version 3.0-SNAPSHOT installed |
| 28 | result.ok, result.status_code are False and 409 |
| 29 | ONOS app igmp, version 3.0-SNAPSHOT installed |
| 30 | Installing cord tester ONOS app /home/ubuntu/cord-tester/src/test/apps/ciena-cordigmp-multitable-3.0-SNAPSHOT.oar |
| 31 | result.ok, result.status_code are False and 409 |
| 32 | Radius server running with IP 11.0.0.3 |
| 33 | Provisioning the ports for the test container |
| 34 | |
| 35 | Running PIPEWORK cmd: pipework enp1s0f0 -i veth0 -l l1 cord-tester1 192.168.100.1/24 02:03:04:00:00:01 |
| 36 | RTNETLINK answers: File exists |
| 37 | Running PIPEWORK cmd: pipework enp1s0f0 -i veth2 -l l2 cord-tester1 192.168.100.2/24 02:03:04:00:00:02 |
| 38 | RTNETLINK answers: File exists |
| 39 | Running PIPEWORK cmd: pipework enp1s0f0 -i veth4 -l l3 cord-tester1 192.168.100.3/24 02:03:04:00:00:03 |
| 40 | RTNETLINK answers: File exists |
| 41 | Running PIPEWORK cmd: pipework enp1s0f0 -i veth6 -l l4 cord-tester1 192.168.100.4/24 02:03:04:00:00:04 |
| 42 | RTNETLINK answers: File exists |
| 43 | Running PIPEWORK cmd: pipework enp1s0f0 -i veth8 -l l5 cord-tester1 192.168.100.5/24 02:03:04:00:00:05 |
| 44 | RTNETLINK answers: File exists |
| 45 | Running PIPEWORK cmd: pipework enp1s0f0 -i veth10 -l l6 cord-tester1 192.168.100.6/24 02:03:04:00:00:06 |
| 46 | RTNETLINK answers: File exists |
| 47 | Running PIPEWORK cmd: pipework enp1s0f0 -i veth12 -l l7 cord-tester1 192.168.100.7/24 02:03:04:00:00:07 |
| 48 | RTNETLINK answers: File exists |
| 49 | Running PIPEWORK cmd: pipework enp1s0f0 -i veth14 -l l8 cord-tester1 192.168.100.8/24 02:03:04:00:00:08 |
| 50 | RTNETLINK answers: File exists |
| 51 | Running PIPEWORK cmd: pipework enp1s0f0 -i veth16 -l l9 cord-tester1 192.168.100.9/24 02:03:04:00:00:09 |
| 52 | RTNETLINK answers: File exists |
| 53 | Running PIPEWORK cmd: pipework enp1s0f0 -i veth18 -l l10 cord-tester1 192.168.100.10/24 02:03:04:00:00:0a |
| 54 | RTNETLINK answers: File exists |
| 55 | Running PIPEWORK cmd: pipework enp1s0f0 -i veth20 -l l11 cord-tester1 192.168.100.11/24 02:03:04:00:00:0b |
| 56 | RTNETLINK answers: File exists |
| 57 | Running PIPEWORK cmd: pipework enp1s0f0 -i veth22 -l l12 cord-tester1 192.168.100.12/24 02:03:04:00:00:0c |
| 58 | RTNETLINK answers: File exists |
| 59 | Running PIPEWORK cmd: pipework enp1s0f0 -i veth24 -l l13 cord-tester1 192.168.100.13/24 02:03:04:00:00:0d |
| 60 | RTNETLINK answers: File exists |
| 61 | Running PIPEWORK cmd: pipework enp1s0f0 -i veth26 -l l14 cord-tester1 192.168.100.14/24 02:03:04:00:00:0e |
| 62 | RTNETLINK answers: File exists |
| 63 | Running PIPEWORK cmd: pipework enp1s0f0 -i veth28 -l l15 cord-tester1 192.168.100.15/24 02:03:04:00:00:0f |
| 64 | RTNETLINK answers: File exists |
| 65 | Running PIPEWORK cmd: pipework enp1s0f0 -i veth30 -l l16 cord-tester1 192.168.100.16/24 02:03:04:00:00:10 |
| 66 | RTNETLINK answers: File exists |
| 67 | Running PIPEWORK cmd: pipework enp1s0f0 -i veth32 -l l17 cord-tester1 192.168.100.17/24 02:03:04:00:00:11 |
| 68 | RTNETLINK answers: File exists |
| 69 | Running PIPEWORK cmd: pipework enp1s0f0 -i veth34 -l l18 cord-tester1 192.168.100.18/24 02:03:04:00:00:12 |
| 70 | RTNETLINK answers: File exists |
| 71 | Running PIPEWORK cmd: pipework enp1s0f0 -i veth36 -l l19 cord-tester1 192.168.100.19/24 02:03:04:00:00:13 |
| 72 | RTNETLINK answers: File exists |
| 73 | Running PIPEWORK cmd: pipework enp1s0f0 -i veth38 -l l20 cord-tester1 192.168.100.20/24 02:03:04:00:00:14 |
| 74 | RTNETLINK answers: File exists |
| 75 | Running PIPEWORK cmd: pipework enp1s0f0 -i veth40 -l l21 cord-tester1 192.168.100.21/24 02:03:04:00:00:15 |
| 76 | RTNETLINK answers: File exists |
| 77 | Running PIPEWORK cmd: pipework enp1s0f0 -i veth42 -l l22 cord-tester1 192.168.100.22/24 02:03:04:00:00:16 |
| 78 | RTNETLINK answers: File exists |
| 79 | Running PIPEWORK cmd: pipework enp1s0f0 -i veth44 -l l23 cord-tester1 192.168.100.23/24 02:03:04:00:00:17 |
| 80 | RTNETLINK answers: File exists |
| 81 | Running PIPEWORK cmd: pipework enp1s0f0 -i veth46 -l l24 cord-tester1 192.168.100.24/24 02:03:04:00:00:18 |
| 82 | RTNETLINK answers: File exists |
| 83 | Running PIPEWORK cmd: pipework enp1s0f0 -i veth48 -l l25 cord-tester1 192.168.100.25/24 |
| 84 | RTNETLINK answers: File exists |
| 85 | Running PIPEWORK cmd: pipework enp1s0f0 -i veth50 -l l26 cord-tester1 192.168.100.26/24 |
| 86 | RTNETLINK answers: File exists |
| 87 | Running PIPEWORK cmd: pipework enp1s0f0 -i veth52 -l l27 cord-tester1 192.168.100.27/24 |
| 88 | RTNETLINK answers: File exists |
| 89 | Running PIPEWORK cmd: pipework enp1s0f0 -i veth54 -l l28 cord-tester1 192.168.100.28/24 |
| 90 | RTNETLINK answers: File exists |
| 91 | Running PIPEWORK cmd: pipework enp1s0f0 -i veth56 -l l29 cord-tester1 192.168.100.29/24 |
| 92 | RTNETLINK answers: File exists |
| 93 | Running PIPEWORK cmd: pipework enp1s0f0 -i veth58 -l l30 cord-tester1 192.168.100.30/24 |
| 94 | RTNETLINK answers: File exists |
| 95 | Running PIPEWORK cmd: pipework enp1s0f0 -i veth60 -l l31 cord-tester1 192.168.100.31/24 |
| 96 | RTNETLINK answers: File exists |
| 97 | Running PIPEWORK cmd: pipework enp1s0f0 -i veth62 -l l32 cord-tester1 192.168.100.32/24 |
| 98 | RTNETLINK answers: File exists |
| 99 | Running PIPEWORK cmd: pipework enp1s0f0 -i veth64 -l l33 cord-tester1 192.168.100.33/24 |
| 100 | RTNETLINK answers: File exists |
| 101 | Running PIPEWORK cmd: pipework enp1s0f0 -i veth66 -l l34 cord-tester1 192.168.100.34/24 |
| 102 | RTNETLINK answers: File exists |
| 103 | Running PIPEWORK cmd: pipework enp1s0f0 -i veth68 -l l35 cord-tester1 192.168.100.35/24 |
| 104 | RTNETLINK answers: File exists |
| 105 | Running PIPEWORK cmd: pipework enp1s0f0 -i veth70 -l l36 cord-tester1 192.168.100.36/24 |
| 106 | RTNETLINK answers: File exists |
| 107 | Provisioning guest port vcpe0 for cord-tester1 with host port: enp1s0f0, s_tag: 222, c_tag: 111 |
| 108 | |
| 109 | RTNETLINK answers: File exists |
| 110 | Provisioning guest port vcpe1 for cord-tester1 with host port: enp1s0f0, s_tag: 304, c_tag: 304 |
| 111 | |
| 112 | RTNETLINK answers: File exists |
| 113 | Provisioning guest port vcpe2 for cord-tester1 with host port: enp1s0f0, s_tag: 304, c_tag: 305 |
| 114 | |
| 115 | RTNETLINK answers: File exists |
| 116 | Provisioning guest port vcpe3 for cord-tester1 with host port: enp1s0f0, s_tag: 304, c_tag: 306 |
| 117 | |
| 118 | RTNETLINK answers: File exists |
| 119 | Provisioning guest port vcpe4 for cord-tester1 with host port: enp1s0f0, s_tag: 304, c_tag: 307 |
| 120 | |
| 121 | RTNETLINK answers: File exists |
| 122 | Provisioning guest port vcpe5 for cord-tester1 with host port: enp1s0f0, s_tag: 304, c_tag: 308 |
| 123 | |
| 124 | RTNETLINK answers: File exists |
| 125 | Provisioning guest port vcpe6 for cord-tester1 with host port: enp1s0f0, s_tag: 304, c_tag: 309 |
| 126 | |
| 127 | RTNETLINK answers: File exists |
| 128 | Provisioning guest port vcpe7 for cord-tester1 with host port: enp1s0f0, s_tag: 304, c_tag: 310 |
| 129 | |
| 130 | RTNETLINK answers: File exists |
| 131 | Provisioning guest port vcpe8 for cord-tester1 with host port: enp1s0f0, s_tag: 304, c_tag: 311 |
| 132 | |
| 133 | RTNETLINK answers: File exists |
| 134 | Test container cord-tester1 started and provisioned to run tests using nosetests |
| 135 | 127.0.0.1 - - [11/Oct/2017 01:56:12] "POST /start HTTP/1.1" 200 - |
| 136 | Running test case dhcpl2relay:dhcpl2relay_exchange.test_dhcpl2relay_delete_and_add_sadis_app |
| 137 | WARNING: No route found for IPv6 destination :: (no default route?) |
| 138 | Controller IP [u'10.70.47.64'], Test type dhcpl2relay:dhcpl2relay_exchange.test_dhcpl2relay_delete_and_add_sadis_app |
| 139 | Installing ONOS cord apps |
| 140 | # Host [10.70.47.64]:8101 found: line 5 |
| 141 | /root/.ssh/known_hosts updated. |
| 142 | Original contents retained as /root/.ssh/known_hosts.old |
| 143 | onoscli: eof exception found |
| 144 | onoscli: logout |
| 145 | |
| 146 | Connection to 10.70.47.64 closed. |
| 147 | |
| 148 | result.ok, result.status_code are False and 409 |
| 149 | ONOS app cord-config, version 3.0-SNAPSHOT installed |
| 150 | result.ok, result.status_code are False and 409 |
| 151 | ONOS app sadis-app, version 3.0-SNAPSHOT installed |
| 152 | result.ok, result.status_code are False and 409 |
| 153 | ONOS app olt-app, version 3.0-SNAPSHOT installed |
| 154 | result.ok, result.status_code are False and 409 |
| 155 | ONOS app aaa, version 3.0-SNAPSHOT installed |
| 156 | result.ok, result.status_code are False and 409 |
| 157 | ONOS app igmp, version 3.0-SNAPSHOT installed |
| 158 | Installing cord tester ONOS app /home/ubuntu/cord-tester/src/test/apps/ciena-cordigmp-multitable-3.0-SNAPSHOT.oar |
| 159 | result.ok, result.status_code are False and 409 |
| 160 | Radius server running with IP 11.0.0.3 |
| 161 | Running ['dhcpl2relay:dhcpl2relay_exchange.test_dhcpl2relay_delete_and_add_sadis_app'] tests across 1 containers in parallel |
| 162 | Modifying scapy tool files before running a test: ['dhcpl2relay:dhcpl2relay_exchange.test_dhcpl2relay_delete_and_add_sadis_app'] |
| 163 | Running tests: ['dhcpl2relay:dhcpl2relay_exchange.test_dhcpl2relay_delete_and_add_sadis_app'] |
| 164 | Connecting to controller at 10.70.47.64 |
| 165 | onoscli: Trying to connect to 10.70.47.64 |
| 166 | Spawning pexpect for ip 10.70.47.64 |
| 167 | ssh connection asked for password, gave password |
| 168 | Command 'summary -j' sent to onoscli. |
| 169 | onoscli: eof exception found |
| 170 | onoscli: logout |
| 171 | |
| 172 | Connection to 10.70.47.64 closed. |
| 173 | |
| 174 | Voltha device of:0001000000000001 not in map. Using uplink vlan 333 |
| 175 | Installing OLT app /root/test/src/test/utils/../apps/olt-app-3.0-SNAPSHOT.oar |
| 176 | Connecting to controller at 10.70.47.64 |
| 177 | onoscli: Trying to connect to 10.70.47.64 |
| 178 | # Host [10.70.47.64]:8101 found: line 1 type RSA |
| 179 | Spawning pexpect for ip 10.70.47.64 |
| 180 | ssh connection asked for password, gave password |
| 181 | Command 'summary -j' sent to onoscli. |
| 182 | onoscli: eof exception found |
| 183 | onoscli: logout |
| 184 | |
| 185 | Connection to 10.70.47.64 closed. |
| 186 | |
| 187 | Running command: ip link add link veth48 name veth48.333 type vlan id 333 |
| 188 | RTNETLINK answers: File exists |
| 189 | Running command: ip link set veth48.333 up |
| 190 | Running command: ip link add link veth48.333 name veth48.333.254 type vlan id 254 |
| 191 | RTNETLINK answers: File exists |
| 192 | Running command: ip link set veth48.333.254 up |
| 193 | Configuring OVS flow for port 37, s_tag 333 |
| 194 | test_dhcpl2relay_delete_and_add_sadis_app (dhcpl2relay.dhcpl2relayTest.dhcpl2relay_exchange) ... # Host [10.70.47.64]:8101 found: line 1 type RSA |
| 195 | Uninstall the sadis app from onos ,app version = /root/test/src/test/dhcpl2relay/../apps/sadis-app-3.0-SNAPSHOT.oar |
| 196 | Installing the sadis app in onos again, app version = /root/test/src/test/dhcpl2relay/../apps/sadis-app-3.0-SNAPSHOT.oar |
| 197 | Got dhcp client IP 192.168.1.11 from server 192.168.1.2 for mac 02:03:04:00:00:01 |
| 198 | |
| 199 | Test test_dhcpl2relay_delete_and_add_sadis_app has errors and warnings |
| 200 | |
| 201 | 2017-10-11 08:56:57,530 | WARN | f-event-stats-27 | FlowModBuilderVer13 | 194 - org.onosproject.onos-providers-openflow-flow - 1.10.6 | Match type INNER_VLAN_VID not yet implemented. |
| 202 | 2017-10-11 08:57:02,529 | WARN | of-event-stats-2 | FlowModBuilderVer13 | 194 - org.onosproject.onos-providers-openflow-flow - 1.10.6 | Match type INNER_VLAN_VID not yet implemented. |
| 203 | 2017-10-11 08:57:05,722 | WARN | vice-installer-5 | DistributedFlowRuleStore | 129 - org.onosproject.onos-core-dist - 1.10.6 | No master for of:00002ec0feee2d4b : flows will be marked for removal |
| 204 | 2017-10-11 08:57:05,723 | WARN | vice-installer-9 | DistributedFlowRuleStore | 129 - org.onosproject.onos-core-dist - 1.10.6 | No master for of:00002ec0feee2d4b : flows will be marked for removal |
| 205 | ok |
| 206 | |
| 207 | ---------------------------------------------------------------------- |
| 208 | Ran 1 test in 46.245s |
| 209 | |
| 210 | OK |
| 211 | Test dhcpl2relayTest.py:dhcpl2relay_exchange.test_dhcpl2relay_delete_and_add_sadis_app Success |
| 212 | Done running tests |
| 213 | 127.0.0.1 - - [11/Oct/2017 01:57:11] "POST /test HTTP/1.1" 200 - |
| 214 | ubuntu@olt-tester:~/cord-tester/src/test/setup$ |
| 215 | |