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