Bug 4603

Summary: [Autobuilder] ssh can't connect to QEMU
Product: [QA/Testing] Runtime Testing Reporter: Bogdan Marinescu <bogdan.a.marinescu>
Component: generalAssignee: Alexandru Georgescu <alexandru.c.georgescu>
Status: VERIFIED FIXED QA Contact:
Severity: normal    
Priority: Medium CC: sgw, sstncr
Version: unspecified   
Target Milestone: 1.5   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Bogdan Marinescu 2013-06-04 07:11:47 UTC 
http://autobuilder.yoctoproject.org:8011/builders/nightly-qa-extras/builds/37/steps/Running%20Sanity%20Tests_1/logs/stdio

 Target IP is 192.168.7.2
| 	Test_Info: IP 192.168.7.2 is up
| 	Test_Info: Qemu Network is up, ping with 192.168.7.2 is OK within 0 seconds
| 	Test_Info: Begin to Test SSH Service in Qemu
| spawn ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no root@192.168.7.2 hostname
| ssh: connect to host 192.168.7.2 port 22: Connection refused
| spawn ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no root@192.168.7.2 hostname
| ssh: connect to host 192.168.7.2 port 22: Connection refused
| spawn ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no root@192.168.7.2 hostname
| ssh: connect to host 192.168.7.2 port 22: Connection refused
| spawn ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no root@192.168.7.2 hostname
| ssh: connect to host 192.168.7.2 port 22: Connection refused
| spawn ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no root@192.168.7.2 hostname
| ssh: connect to host 192.168.7.2 port 22: Connection refused
| 	Test_Info: We can not ssh on 192.168.7.2 in 50 seconds
| 	Test_Info: SSH Test FAIL
Comment 1 Stefan Stanacar 2013-06-04 09:04:49 UTC 
This might be relevant http://autobuilder.yoctoproject.org:8011/builders/nightly-qa-extras/builds/37/steps/CreateAutoConf_1/logs/stdio
in particular: 
IMAGE_FEATURES_append = " read-only-rootfs"

That's a read only /, but that shouldn't stop ssh work, imho.
Comment 2 Stefan Stanacar 2013-06-04 15:40:21 UTC 
And indeed ssh does work. I can't reproduce on my local AB instance or when building and starting tests manually:

IMAGE_FEATURES_append = " read-only-rootfs"
IMAGETEST = "qemu"
TEST_SCENE = "sanity:boot sanity:ssh"

bitbake core-image-sato

It does seem to boot a little slower than a non read only image.
So most likely this is a timeout - if the test can't connect in 50 seconds it gives up - and if the AB is somewhat loaded, the image might boot a bit slower. 
The thing is the ssh test has a 400 seconds timeout but that gets overwriteen when TEST_SERIALIZE is set :( (which is by default) and becomes 50, so this is an unfortunately situation on the AB: a slower to boot image, an overloaded AB, a small timeout. 

Again I wasn't able to reproduce manually or on a AB instance (which has the same config as the public AB).
Comment 3 Alexandru Georgescu 2013-08-22 07:13:25 UTC 
Closing this since it's an old one and Stefan couldn't reproduce.
Comment 4 Alexandru Georgescu 2013-09-30 12:19:53 UTC 
.