waiting for network probing up may fail before default timeout

Bug #813394 reported by Spring Zhang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
LAVA Dispatcher
Invalid
Undecided
Unassigned

Bug Description

I observed wait_network_up could fail on some of my board for the network probe up with a latency, it will fail before timeout.

So a previous patch of mine can't work, I suggest to use time.sleep(timeout) to make it more reliable.

The logs from my board, it only detect 4 times and network reports failure, but the timeout is far away reached:

 * Documentation: http://www.linaro.org
                                                                         [ OK ]
root@master:~# Waiting for network to come up
LC_ALL=C ping -W4 -c1 192.168.12.8
LC_ALL=C ping -W4 -c1 192.168.12.8
connect: Network is unreachable
root@master:~# LC_ALL=C ping -W4 -c1 192.168.12.8
LC_ALL=C ping -W4 -c1 192.168.12.8
connect: Network is unreachable
root@master:~# LC_ALL=C ping -W4 -c1 192.168.12.8

root@master:~# Lava failed at action deploy_linaro_image with error: Network can't probe up when deployment

Related branches

Revision history for this message
Paul Larson (pwlars) wrote :

It should be trying more than 4 times in the 2 minutes that it currently waits. How long does it take each time before ping exits?

Revision history for this message
Spring Zhang (qzhang) wrote :

It needs less than 2 minutes, at most 30 seconds, does the code always work for other boards in you tests?
If yes, I doubt it's a bug in i.MX board, like serial character truncation issue. It can't get a respond at the last ping cmd.

Revision history for this message
Spring Zhang (qzhang) wrote :

The issue is more possible related with serial port, on my target, it send a 'ping' but no cmd result resturn before a timeout.

Revision history for this message
Spring Zhang (qzhang) wrote :

let's consider it invalid, I can't find the root cause and it seems only on my board.

Changed in lava-dispatcher:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.