I’ve compared the “working” and “non-working” kernel logs and there are only two differences I can find.
1) In the non working one it has to run an fsck: https://validation.linaro.org/scheduler/job/845472/log_file#L_349_223 https://validation.linaro.org/scheduler/job/845472/log_file#L_349_223 - I can’t imagine that this is causing the problem
2) A little later on, you see it tries to bring the network interfaces up: - Working one: https://validation.linaro.org/scheduler/job/845552/log_file#L_285_9 https://validation.linaro.org/scheduler/job/845552/log_file#L_285_9 - Non working one: https://validation.linaro.org/scheduler/job/845472/log_file#L_351_10 https://validation.linaro.org/scheduler/job/845472/log_file#L_351_10 - You can see that the non working one is saying that “lo” and “eth0” are both already up.
They are the same images, so I don’t quite understand how we get into this state.
Dave
On 24 Apr 2016, at 18:03, Leo Yan leo.yan@linaro.org wrote:
Hi there,
When I run LAVA hacking session on Juno but found sometimes Juno cannot be allocated IP properly:
- I created multinode definition for Juno:
https://validation.linaro.org/scheduler/job/845471.0: this definition is to launch kvm so I can run testing suits on it; https://validation.linaro.org/scheduler/job/845471.1: this definition is to launch "deploy_linaro_image" on Juno board;
- After launched these two images, the kvm usually can work well and I
can smoothly log in it with ssh;
- But for juno board, it will have below log for ssh:
395.1 ./setup_session_oe: line 38: /etc/init.d/ssh: No such file or directory 395.2 <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=sshd-restart RESULT=fail> 395.3 sshd re-start failed 395.4 Target's Gateway: 10.0.0.1 395.5 ip: RTNETLINK answers: Network is unreachable 395.6 395.7 395.8 ********************************************************************************************* 395.9 Please connect to: ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no root@ (juno-07) 395.10 ********************************************************************************************* 395.11
So finally I cannot get the info for Juno's IP and cannot log in it with ssh. It's not everytime I can reproduce this failure, so sometimes it's lucky so I can get a correct IP.
- As a workaroud, I found if I create two saperated definitions for
Juno and kvm independently, then Juno's IP issue can be resolved:
https://validation.linaro.org/scheduler/job/845552 https://validation.linaro.org/scheduler/job/845561
So could you help give suggestions for this?
Thanks, Leo Yan