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