Bug 136

Summary: Can not access poky-image-minimal/sato via ssh
Product: [Build System, Metadata & Runtime] Meta-yocto Reporter: Jiajun Xu <jiajun.xu>
Component: meta-yoctoAssignee: Saul Wold <sgw>
Status: VERIFIED DUPLICATE QA Contact:
Severity: normal    
Priority: Medium CC: poky.bs.watcher, poky.watcher, richard.purdie, yongkang.you
Version: unspecified   
Target Milestone: ---   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Program Management Documentation change: ---

Description Jiajun Xu 2010-07-22 07:36:24 UTC
Testing Env:    
Host: Ubuntu 10.04 LTS
Kernel: 2.6.32-21-generic-pae
Poky gitinfo(used to build qemu-native):
0c3b1aa0a5461c9b5f3833feb091f7c8a459ca9b (git://git.pokylinux.org/poky.git)
all these images from weekly build (20100721) on autobuilder,
http://yoctobuild01.jf.intel.com/build-areas/weekly-release/build/build/tmp/deploy/images/.

With images from weekly builds 20100721, most poky-image-minimal/sato images have no ssh service accessible. (except for qemuarm poky-image-sato)
They are:
qemux86 poky-image-minimal/sato
qemuarm poky-image-minimal
qemumips poky-image-minimal (sato images fail to boot up)
qemuppc poky-image-minimal/sato
Comment 1 Saul Wold 2010-07-27 18:33:36 UTC
Possibly due to running out of Inodes during creation of SSH Key

*** This bug has been marked as a duplicate of bug 130 ***
Comment 2 Jiajun Xu 2010-09-01 22:47:29 UTC
Mark the bug as verified since we do not meet the issue any more.