Chetan Gaonker | a58c258 | 2017-08-02 00:02:04 +0000 | [diff] [blame^] | 1 | ubuntu@cord-rs-s8:~/cord-tester/src/test/setup$ sudo ./cord-test.py run -m manifest-ponsim.json -t voltha:voltha_exchange.test_two_subscribers_with_voltha_for_igmp_multiple_times_toggling_uni_port_for_one_subscriber_verifying_traffic |
| 2 | # Host [172.17.0.2]:8101 found: line 3 type RSA |
| 3 | onoscli: eof exception found |
| 4 | onoscli: logout |
| 5 | |
| 6 | Connection to 172.17.0.2 closed. |
| 7 | |
| 8 | result.ok, result.status_code are False and 409 |
| 9 | ONOS app cord-config, version 2.0-SNAPSHOT installed |
| 10 | result.ok, result.status_code are False and 409 |
| 11 | ONOS app aaa, version 2.0-SNAPSHOT installed |
| 12 | result.ok, result.status_code are False and 409 |
| 13 | ONOS app igmp, version 2.0-SNAPSHOT installed |
| 14 | Controller IP [u'172.17.0.2'], Test type voltha:voltha_exchange.test_two_subscribers_with_voltha_for_igmp_multiple_times_toggling_uni_port_for_one_subscriber_verifying_traffic |
| 15 | Installing cord tester ONOS app /home/ubuntu/cord-tester/src/test/apps/ciena-cordigmp-multitable-3.0-SNAPSHOT.oar |
| 16 | result.ok, result.status_code are False and 409 |
| 17 | WARNING: The DOCKER_HOST_IP variable is not set. Defaulting to a blank string. |
| 18 | compose_consul_1 is up-to-date |
| 19 | compose_zookeeper_1 is up-to-date |
| 20 | compose_fluentd_1 is up-to-date |
| 21 | compose_registrator_1 is up-to-date |
| 22 | compose_kafka_1 is up-to-date |
| 23 | IP 172.18.0.2 for service consul |
| 24 | IP 172.18.0.5 for service kafka |
| 25 | IP 172.18.0.4 for service zookeeper |
| 26 | IP 172.18.0.6 for service registrator |
| 27 | IP 172.18.0.3 for service fluentd |
| 28 | Chameleon voltha sevice is already running. Skipped start |
| 29 | VOLTHA core is already running. Skipped start |
| 30 | VOLTHA ofagent is already running. Skipped start |
| 31 | PONSIM already running. Skipped start |
| 32 | Radius server running with IP 172.17.0.3 |
| 33 | Running ['voltha:voltha_exchange.test_two_subscribers_with_voltha_for_igmp_multiple_times_toggling_uni_port_for_one_subscriber_verifying_traffic'] tests across 1 containers in parallel |
| 34 | Starting test container cord-tester1, image cordtest/nose, tag candidate |
| 35 | Provisioning the ports for the test container |
| 36 | |
| 37 | Running PIPEWORK cmd: pipework pon1_128 -i veth0 -l l1 cord-tester1 192.168.100.1/24 |
| 38 | Running PIPEWORK cmd: pipework ponmgmt -i veth2 -l l2 cord-tester1 192.168.100.2/24 |
| 39 | Running PIPEWORK cmd: pipework pon1_129 -i veth4 -l l3 cord-tester1 192.168.100.3/24 |
| 40 | Running PIPEWORK cmd: pipework pon1_130 -i veth6 -l l4 cord-tester1 192.168.100.4/24 |
| 41 | Running PIPEWORK cmd: pipework pon1_131 -i veth8 -l l5 cord-tester1 192.168.100.5/24 |
| 42 | Running PIPEWORK cmd: pipework pon1_132 -i veth10 -l l6 cord-tester1 192.168.100.6/24 |
| 43 | Running PIPEWORK cmd: pipework pon1_133 -i veth12 -l l7 cord-tester1 192.168.100.7/24 |
| 44 | Running PIPEWORK cmd: pipework pon1_134 -i veth14 -l l8 cord-tester1 192.168.100.8/24 |
| 45 | Running PIPEWORK cmd: pipework pon1_135 -i veth16 -l l9 cord-tester1 192.168.100.9/24 |
| 46 | Running PIPEWORK cmd: pipework pon1_136 -i veth18 -l l10 cord-tester1 192.168.100.10/24 |
| 47 | Running PIPEWORK cmd: pipework pon1_137 -i veth20 -l l11 cord-tester1 192.168.100.11/24 |
| 48 | Running PIPEWORK cmd: pipework pon1_128 -i veth22 -l l12 cord-tester1 192.168.100.12/24 |
| 49 | Running PIPEWORK cmd: pipework pon1_129 -i veth24 -l l13 cord-tester1 192.168.100.13/24 |
| 50 | Running PIPEWORK cmd: pipework pon1_130 -i veth26 -l l14 cord-tester1 192.168.100.14/24 |
| 51 | Running PIPEWORK cmd: pipework pon1_131 -i veth28 -l l15 cord-tester1 192.168.100.15/24 |
| 52 | Running PIPEWORK cmd: pipework pon1_132 -i veth30 -l l16 cord-tester1 192.168.100.16/24 |
| 53 | Running PIPEWORK cmd: pipework pon1_133 -i veth32 -l l17 cord-tester1 192.168.100.17/24 |
| 54 | Running PIPEWORK cmd: pipework pon1_134 -i veth34 -l l18 cord-tester1 192.168.100.18/24 |
| 55 | Running PIPEWORK cmd: pipework pon1_135 -i veth36 -l l19 cord-tester1 192.168.100.19/24 |
| 56 | Running PIPEWORK cmd: pipework pon1_136 -i veth38 -l l20 cord-tester1 192.168.100.20/24 |
| 57 | Running PIPEWORK cmd: pipework pon1_137 -i veth40 -l l21 cord-tester1 192.168.100.21/24 |
| 58 | Running PIPEWORK cmd: pipework pon1_138 -i veth42 -l l22 cord-tester1 192.168.100.22/24 |
| 59 | Modifying scapy tool files before running a test: ['voltha:voltha_exchange.test_two_subscribers_with_voltha_for_igmp_multiple_times_toggling_uni_port_for_one_subscriber_verifying_traffic'] |
| 60 | Running tests: ['voltha:voltha_exchange.test_two_subscribers_with_voltha_for_igmp_multiple_times_toggling_uni_port_for_one_subscriber_verifying_traffic'] |
| 61 | WARNING: No route found for IPv6 destination :: (no default route?) |
| 62 | Connecting to controller at 172.17.0.2 |
| 63 | onoscli: Trying to connect to 172.17.0.2 |
| 64 | Spawning pexpect for ip 172.17.0.2 |
| 65 | ssh connection asked for password, gave password |
| 66 | Command 'summary -j' sent to onoscli. |
| 67 | onoscli: eof exception found |
| 68 | onoscli: logout |
| 69 | |
| 70 | Connection to 172.17.0.2 closed. |
| 71 | |
| 72 | Installing the multi table app /root/test/src/test/voltha/../apps/ciena-cordigmp-multitable-3.0-SNAPSHOT.oar for subscriber test |
| 73 | Test Method: ... Enabling ponsim olt |
| 74 | Pre-provisioning ponsim_olt with address 172.17.0.1:50060 |
| 75 | Enabling device 005bd47606cb |
| 76 | Checking operational status for device 005bd47606cb |
| 77 | Installing OLT app |
| 78 | Adding subscribers through OLT app |
| 79 | 172.17.0.4 - - [01/Aug/2017 10:27:59] "POST /RPC2 HTTP/1.1" 200 - |
| 80 | Adding group 225.0.0.1 |
| 81 | Adding group 225.0.0.1 |
| 82 | Admin state of uni port is down and up after delay of 30 sec during igmp flow check on voltha |
| 83 | Admin state of uni_port is down |
| 84 | All subscribers have joined the channel |
| 85 | Subscriber on port veth4 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 86 | All subscribers have joined the channel |
| 87 | Subscriber on port veth0 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 88 | Subscriber on port veth4 timed out |
| 89 | Subscriber on port veth0 timed out |
| 90 | Joining channel 0 for subscriber port veth4 |
| 91 | All subscribers have joined the channel |
| 92 | Subscriber on port veth4 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 93 | Joining channel 0 for subscriber port veth0 |
| 94 | All subscribers have joined the channel |
| 95 | Subscriber on port veth0 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 96 | Subscriber on port veth4 timed out |
| 97 | Subscriber on port veth0 timed out |
| 98 | Joining channel 0 for subscriber port veth4 |
| 99 | All subscribers have joined the channel |
| 100 | Admin state of uni_port is up now |
| 101 | Subscriber on port veth4 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 102 | Joining channel 0 for subscriber port veth0 |
| 103 | All subscribers have joined the channel |
| 104 | Subscriber on port veth0 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 105 | Subscriber on port veth4 timed out |
| 106 | Subscriber on port veth0 timed out |
| 107 | Joining channel 0 for subscriber port veth4 |
| 108 | All subscribers have joined the channel |
| 109 | Subscriber on port veth4 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 110 | Joining channel 0 for subscriber port veth0 |
| 111 | All subscribers have joined the channel |
| 112 | Subscriber on port veth0 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 113 | Subscriber on port veth4 timed out |
| 114 | Subscriber on port veth0 timed out |
| 115 | Joining channel 0 for subscriber port veth4 |
| 116 | All subscribers have joined the channel |
| 117 | Subscriber on port veth4 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 118 | Admin state of uni port is down and up after delay of 30 sec during igmp flow check on voltha |
| 119 | Admin state of uni_port is down |
| 120 | Joining channel 0 for subscriber port veth0 |
| 121 | All subscribers have joined the channel |
| 122 | Subscriber on port veth0 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 123 | Subscriber on port veth4 timed out |
| 124 | Subscriber on port veth0 timed out |
| 125 | Joining channel 0 for subscriber port veth4 |
| 126 | All subscribers have joined the channel |
| 127 | Subscriber on port veth4 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 128 | Joining channel 0 for subscriber port veth0 |
| 129 | All subscribers have joined the channel |
| 130 | Subscriber on port veth0 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 131 | Subscriber on port veth4 timed out |
| 132 | Subscriber on port veth0 timed out |
| 133 | Joining channel 0 for subscriber port veth4 |
| 134 | All subscribers have joined the channel |
| 135 | Subscriber on port veth4 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 136 | Joining channel 0 for subscriber port veth0 |
| 137 | Admin state of uni_port is up now |
| 138 | All subscribers have joined the channel |
| 139 | Subscriber on port veth0 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 140 | Subscriber on port veth4 timed out |
| 141 | Subscriber on port veth0 timed out |
| 142 | Joining channel 0 for subscriber port veth4 |
| 143 | All subscribers have joined the channel |
| 144 | Subscriber on port veth4 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 145 | Joining channel 0 for subscriber port veth0 |
| 146 | All subscribers have joined the channel |
| 147 | Subscriber on port veth0 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 148 | Subscriber on port veth4 timed out |
| 149 | Subscriber on port veth0 timed out |
| 150 | Joining channel 0 for subscriber port veth4 |
| 151 | All subscribers have joined the channel |
| 152 | Subscriber on port veth4 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 153 | Joining channel 0 for subscriber port veth0 |
| 154 | Admin state of uni port is down and up after delay of 30 sec during igmp flow check on voltha |
| 155 | Admin state of uni_port is down |
| 156 | All subscribers have joined the channel |
| 157 | Subscriber on port veth0 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 158 | Subscriber on port veth4 timed out |
| 159 | Subscriber on port veth0 timed out |
| 160 | Joining channel 0 for subscriber port veth4 |
| 161 | All subscribers have joined the channel |
| 162 | Subscriber on port veth4 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 163 | Joining channel 0 for subscriber port veth0 |
| 164 | All subscribers have joined the channel |
| 165 | Subscriber on port veth0 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 166 | Subscriber on port veth4 timed out |
| 167 | Subscriber on port veth0 timed out |
| 168 | Joining channel 0 for subscriber port veth4 |
| 169 | All subscribers have joined the channel |
| 170 | Subscriber on port veth4 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 171 | Joining channel 0 for subscriber port veth0 |
| 172 | Admin state of uni_port is up now |
| 173 | All subscribers have joined the channel |
| 174 | Subscriber on port veth0 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 175 | Subscriber on port veth4 timed out |
| 176 | Subscriber on port veth0 timed out |
| 177 | Joining channel 0 for subscriber port veth4 |
| 178 | This service is failed and other services will not run for this subscriber |
| 179 | This Subscriber is tested for multiple service eligibility |
| 180 | Joining channel 0 for subscriber port veth0 |
| 181 | This service is failed and other services will not run for this subscriber |
| 182 | This Subscriber is tested for multiple service eligibility |
| 183 | Deleted subscriber for device of:0000000000000001 on port 128 |
| 184 | Deleted subscriber for device of:0000000000000001 on port 129 |
| 185 | Deleted subscriber for device of:0000000000000001 on port 130 |
| 186 | Deleted subscriber for device of:0000000000000001 on port 131 |
| 187 | Deleted subscriber for device of:0000000000000001 on port 132 |
| 188 | Deleted subscriber for device of:0000000000000001 on port 133 |
| 189 | Deleted subscriber for device of:0000000000000001 on port 134 |
| 190 | Deleted subscriber for device of:0000000000000001 on port 135 |
| 191 | Deleted subscriber for device of:0000000000000001 on port 136 |
| 192 | Deleted subscriber for device of:0000000000000001 on port 137 |
| 193 | Deleted subscriber for device of:0000000000000001 on port 138 |
| 194 | Disabling device 005bd47606cb |
| 195 | Admin state of uni port is down and up after delay of 30 sec during igmp flow check on voltha |
| 196 | Admin state of uni_port is down |
| 197 | Deleting device 005bd47606cb |
| 198 | Uninstalling OLT app |
| 199 | Exception in thread Thread-2: |
| 200 | Traceback (most recent call last): |
| 201 | File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner |
| 202 | self.run() |
| 203 | File "/usr/lib/python2.7/threading.py", line 763, in run |
| 204 | self.__target(*self.__args, **self.__kwargs) |
| 205 | File "/root/test/src/test/voltha/volthaTest.py", line 1444, in voltha_subscribers |
| 206 | assert_equal(test_status, True) |
| 207 | File "/usr/lib/python2.7/unittest/case.py", line 515, in assertEqual |
| 208 | assertion_func(first, second, msg=msg) |
| 209 | File "/usr/lib/python2.7/unittest/case.py", line 508, in _baseAssertEqual |
| 210 | raise self.failureException(msg) |
| 211 | AssertionError: False != True |
| 212 | |
| 213 | Admin state of uni_port is up now |
| 214 | Admin state of uni port is down and up after delay of 30 sec during igmp flow check on voltha |
| 215 | Admin state of uni_port is down |
| 216 | Admin state of uni_port is up now |
| 217 | Unhandled Error |
| 218 | Traceback (most recent call last): |
| 219 | File "/usr/lib/python2.7/threading.py", line 763, in run |
| 220 | self.__target(*self.__args, **self.__kwargs) |
| 221 | File "/usr/local/lib/python2.7/dist-packages/nose-1.3.7-py2.7.egg/nose/twistedtools.py", line 57, in <lambda> |
| 222 | installSignalHandlers=False)) |
| 223 | File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 1192, in run |
| 224 | self.mainLoop() |
| 225 | File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 1201, in mainLoop |
| 226 | self.runUntilCurrent() |
| 227 | --- <exception caught here> --- |
| 228 | File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 824, in runUntilCurrent |
| 229 | call.func(*call.args, **call.kw) |
| 230 | File "/root/test/src/test/voltha/volthaTest.py", line 5256, in igmp_flow_check_operating_onu_admin_state |
| 231 | assert_equal(self.success, True) |
| 232 | File "/usr/lib/python2.7/unittest/case.py", line 515, in assertEqual |
| 233 | assertion_func(first, second, msg=msg) |
| 234 | File "/usr/lib/python2.7/unittest/case.py", line 508, in _baseAssertEqual |
| 235 | raise self.failureException(msg) |
| 236 | exceptions.AssertionError: False != True |
| 237 | FAIL |
| 238 | Installing back the cord igmp app /root/test/src/test/voltha/../apps/ciena-cordigmp-3.0-SNAPSHOT.oar for subscriber test on exit |
| 239 | |
| 240 | ====================================================================== |
| 241 | FAIL: Test Method: |
| 242 | ---------------------------------------------------------------------- |
| 243 | Traceback (most recent call last): |
| 244 | File "/usr/local/lib/python2.7/dist-packages/nose-1.3.7-py2.7.egg/nose/twistedtools.py", line 165, in wrapper |
| 245 | % timeout) |
| 246 | TimeExpired: timeout expired before end of test (500.000000 s.) |
| 247 | -------------------- >> begin captured stdout << --------------------- |
| 248 | result.ok, result.status_code are True and 200 |
| 249 | |
| 250 | --------------------- >> end captured stdout << ---------------------- |
| 251 | -------------------- >> begin captured logging << -------------------- |
| 252 | scapy.runtime: WARNING: No route found for IPv6 destination :: (no default route?) |
| 253 | docker.auth.auth: DEBUG: Trying paths: ['/root/.docker/config.json', '/root/.dockercfg'] |
| 254 | docker.auth.auth: DEBUG: No config file found |
| 255 | docker.auth.auth: DEBUG: Trying paths: ['/root/.docker/config.json', '/root/.dockercfg'] |
| 256 | docker.auth.auth: DEBUG: No config file found |
| 257 | cordTester: INFO: Connecting to controller at 172.17.0.2 |
| 258 | cordTester: INFO: onoscli: Trying to connect to 172.17.0.2 |
| 259 | onoscli: INFO: |
| 260 | cordTester: INFO: Spawning pexpect for ip 172.17.0.2 |
| 261 | cordTester: INFO: ssh connection asked for password, gave password |
| 262 | cordTester: INFO: Command 'summary -j' sent to onoscli. |
| 263 | cordTester: ERROR: onoscli: eof exception found |
| 264 | cordTester: ERROR: onoscli: logout |
| 265 | |
| 266 | Connection to 172.17.0.2 closed. |
| 267 | |
| 268 | cordTester: INFO: Installing the multi table app /root/test/src/test/voltha/../apps/ciena-cordigmp-multitable-3.0-SNAPSHOT.oar for subscriber test |
| 269 | cordTester: INFO: Enabling ponsim olt |
| 270 | cordTester: INFO: Pre-provisioning ponsim_olt with address 172.17.0.1:50060 |
| 271 | cordTester: INFO: Enabling device 005bd47606cb |
| 272 | cordTester: INFO: Checking operational status for device 005bd47606cb |
| 273 | cordTester: INFO: Installing OLT app |
| 274 | cordTester: INFO: Adding subscribers through OLT app |
| 275 | cordTester: DEBUG: Adding group 225.0.0.1 |
| 276 | cordTester: DEBUG: Adding group 225.0.0.1 |
| 277 | cordTester: INFO: Admin state of uni port is down and up after delay of 30 sec during igmp flow check on voltha |
| 278 | cordTester: INFO: Admin state of uni_port is down |
| 279 | cordTester: INFO: All subscribers have joined the channel |
| 280 | cordTester: INFO: Subscriber on port veth4 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 281 | cordTester: INFO: All subscribers have joined the channel |
| 282 | cordTester: INFO: Subscriber on port veth0 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 283 | cordTester: INFO: Subscriber on port veth4 timed out |
| 284 | cordTester: INFO: Subscriber on port veth0 timed out |
| 285 | cordTester: INFO: Joining channel 0 for subscriber port veth4 |
| 286 | cordTester: INFO: All subscribers have joined the channel |
| 287 | cordTester: INFO: Subscriber on port veth4 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 288 | cordTester: INFO: Joining channel 0 for subscriber port veth0 |
| 289 | cordTester: INFO: All subscribers have joined the channel |
| 290 | cordTester: INFO: Subscriber on port veth0 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 291 | cordTester: INFO: Subscriber on port veth4 timed out |
| 292 | cordTester: INFO: Subscriber on port veth0 timed out |
| 293 | cordTester: INFO: Joining channel 0 for subscriber port veth4 |
| 294 | cordTester: INFO: All subscribers have joined the channel |
| 295 | cordTester: INFO: Admin state of uni_port is up now |
| 296 | cordTester: INFO: Subscriber on port veth4 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 297 | cordTester: INFO: Joining channel 0 for subscriber port veth0 |
| 298 | cordTester: INFO: All subscribers have joined the channel |
| 299 | cordTester: INFO: Subscriber on port veth0 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 300 | cordTester: INFO: Subscriber on port veth4 timed out |
| 301 | cordTester: INFO: Subscriber on port veth0 timed out |
| 302 | cordTester: INFO: Joining channel 0 for subscriber port veth4 |
| 303 | cordTester: INFO: All subscribers have joined the channel |
| 304 | cordTester: INFO: Subscriber on port veth4 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 305 | cordTester: INFO: Joining channel 0 for subscriber port veth0 |
| 306 | cordTester: INFO: All subscribers have joined the channel |
| 307 | cordTester: INFO: Subscriber on port veth0 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 308 | cordTester: INFO: Subscriber on port veth4 timed out |
| 309 | cordTester: INFO: Subscriber on port veth0 timed out |
| 310 | cordTester: INFO: Joining channel 0 for subscriber port veth4 |
| 311 | cordTester: INFO: All subscribers have joined the channel |
| 312 | cordTester: INFO: Subscriber on port veth4 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 313 | cordTester: INFO: Admin state of uni port is down and up after delay of 30 sec during igmp flow check on voltha |
| 314 | cordTester: INFO: Admin state of uni_port is down |
| 315 | cordTester: INFO: Joining channel 0 for subscriber port veth0 |
| 316 | cordTester: INFO: All subscribers have joined the channel |
| 317 | cordTester: INFO: Subscriber on port veth0 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 318 | cordTester: INFO: Subscriber on port veth4 timed out |
| 319 | cordTester: INFO: Subscriber on port veth0 timed out |
| 320 | cordTester: INFO: Joining channel 0 for subscriber port veth4 |
| 321 | cordTester: INFO: All subscribers have joined the channel |
| 322 | cordTester: INFO: Subscriber on port veth4 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 323 | cordTester: INFO: Joining channel 0 for subscriber port veth0 |
| 324 | cordTester: INFO: All subscribers have joined the channel |
| 325 | cordTester: INFO: Subscriber on port veth0 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 326 | cordTester: INFO: Subscriber on port veth4 timed out |
| 327 | cordTester: INFO: Subscriber on port veth0 timed out |
| 328 | cordTester: INFO: Joining channel 0 for subscriber port veth4 |
| 329 | cordTester: INFO: All subscribers have joined the channel |
| 330 | cordTester: INFO: Subscriber on port veth4 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 331 | cordTester: INFO: Joining channel 0 for subscriber port veth0 |
| 332 | cordTester: INFO: Admin state of uni_port is up now |
| 333 | cordTester: INFO: All subscribers have joined the channel |
| 334 | cordTester: INFO: Subscriber on port veth0 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 335 | cordTester: INFO: Subscriber on port veth4 timed out |
| 336 | cordTester: INFO: Subscriber on port veth0 timed out |
| 337 | cordTester: INFO: Joining channel 0 for subscriber port veth4 |
| 338 | cordTester: INFO: All subscribers have joined the channel |
| 339 | cordTester: INFO: Subscriber on port veth4 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 340 | cordTester: INFO: Joining channel 0 for subscriber port veth0 |
| 341 | cordTester: INFO: All subscribers have joined the channel |
| 342 | cordTester: INFO: Subscriber on port veth0 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 343 | cordTester: INFO: Subscriber on port veth4 timed out |
| 344 | cordTester: INFO: Subscriber on port veth0 timed out |
| 345 | cordTester: INFO: Joining channel 0 for subscriber port veth4 |
| 346 | cordTester: INFO: All subscribers have joined the channel |
| 347 | cordTester: INFO: Subscriber on port veth4 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 348 | cordTester: INFO: Joining channel 0 for subscriber port veth0 |
| 349 | cordTester: INFO: Admin state of uni port is down and up after delay of 30 sec during igmp flow check on voltha |
| 350 | cordTester: INFO: Admin state of uni_port is down |
| 351 | cordTester: INFO: All subscribers have joined the channel |
| 352 | cordTester: INFO: Subscriber on port veth0 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 353 | cordTester: INFO: Subscriber on port veth4 timed out |
| 354 | cordTester: INFO: Subscriber on port veth0 timed out |
| 355 | cordTester: INFO: Joining channel 0 for subscriber port veth4 |
| 356 | cordTester: INFO: All subscribers have joined the channel |
| 357 | cordTester: INFO: Subscriber on port veth4 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 358 | cordTester: INFO: Joining channel 0 for subscriber port veth0 |
| 359 | cordTester: INFO: All subscribers have joined the channel |
| 360 | cordTester: INFO: Subscriber on port veth0 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 361 | cordTester: INFO: Subscriber on port veth4 timed out |
| 362 | cordTester: INFO: Subscriber on port veth0 timed out |
| 363 | cordTester: INFO: Joining channel 0 for subscriber port veth4 |
| 364 | cordTester: INFO: All subscribers have joined the channel |
| 365 | cordTester: INFO: Subscriber on port veth4 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 366 | cordTester: INFO: Joining channel 0 for subscriber port veth0 |
| 367 | cordTester: INFO: Admin state of uni_port is up now |
| 368 | cordTester: INFO: All subscribers have joined the channel |
| 369 | cordTester: INFO: Subscriber on port veth0 checking data traffic receiving from group 225.0.0.1, channel 0 |
| 370 | cordTester: INFO: Subscriber on port veth4 timed out |
| 371 | cordTester: INFO: Subscriber on port veth0 timed out |
| 372 | cordTester: INFO: Joining channel 0 for subscriber port veth4 |
| 373 | cordTester: INFO: This service is failed and other services will not run for this subscriber |
| 374 | cordTester: INFO: This Subscriber is tested for multiple service eligibility |
| 375 | cordTester: INFO: Joining channel 0 for subscriber port veth0 |
| 376 | cordTester: INFO: This service is failed and other services will not run for this subscriber |
| 377 | cordTester: INFO: This Subscriber is tested for multiple service eligibility |
| 378 | cordTester: INFO: Deleted subscriber for device of:0000000000000001 on port 128 |
| 379 | cordTester: INFO: Deleted subscriber for device of:0000000000000001 on port 129 |
| 380 | cordTester: INFO: Deleted subscriber for device of:0000000000000001 on port 130 |
| 381 | cordTester: INFO: Deleted subscriber for device of:0000000000000001 on port 131 |
| 382 | cordTester: INFO: Deleted subscriber for device of:0000000000000001 on port 132 |
| 383 | cordTester: INFO: Deleted subscriber for device of:0000000000000001 on port 133 |
| 384 | cordTester: INFO: Deleted subscriber for device of:0000000000000001 on port 134 |
| 385 | cordTester: INFO: Deleted subscriber for device of:0000000000000001 on port 135 |
| 386 | cordTester: INFO: Deleted subscriber for device of:0000000000000001 on port 136 |
| 387 | cordTester: INFO: Deleted subscriber for device of:0000000000000001 on port 137 |
| 388 | cordTester: INFO: Deleted subscriber for device of:0000000000000001 on port 138 |
| 389 | cordTester: INFO: Disabling device 005bd47606cb |
| 390 | cordTester: INFO: Admin state of uni port is down and up after delay of 30 sec during igmp flow check on voltha |
| 391 | cordTester: INFO: Admin state of uni_port is down |
| 392 | cordTester: INFO: Deleting device 005bd47606cb |
| 393 | cordTester: INFO: Uninstalling OLT app |
| 394 | cordTester: INFO: Admin state of uni_port is up now |
| 395 | cordTester: INFO: Admin state of uni port is down and up after delay of 30 sec during igmp flow check on voltha |
| 396 | cordTester: INFO: Admin state of uni_port is down |
| 397 | cordTester: INFO: Admin state of uni_port is up now |
| 398 | --------------------- >> end captured logging << --------------------- |
| 399 | |
| 400 | ---------------------------------------------------------------------- |
| 401 | Ran 1 test in 524.042s |
| 402 | |
| 403 | FAILED (failures=1) |
| 404 | Test volthaTest.py:voltha_exchange.test_two_subscribers_with_voltha_for_igmp_multiple_times_toggling_uni_port_for_one_subscriber_verifying_traffic Failure |
| 405 | Done running tests |
| 406 | Removing test container cord-tester1 |
| 407 | ubuntu@cord-rs-s8:~/cord-tester/src/test/setup$ |
| 408 | |