Bug 12251

Summary: [ross/mut] nightly-oe-selftest failed
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Armin Kuster <akuster>
Component: coreAssignee: Ross Burton <ross.burton>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium+ CC: meta.mr.watcher, meta.watcher
Version: 2.4.1   
Target Milestone: 2.5 M1   
Hardware: x86   
OS: Multiple   
URL: https://autobuilder.yocto.io/builders/nightly-oe-selftest/builds/569/steps/Running oe-selftest/logs/stdio
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know

Description Armin Kuster 2017-10-19 03:23:56 UTC
2017-10-17 21:20:07,934 - oe-selftest - INFO - Traceback (most recent call last):
  File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-oe-selftest/build/meta/lib/oeqa/selftest/cases/runtime_test.py", line 266, in test_postinst_rootfs_and_boot
    result = runCmd('ssh %s root@%s %s' % (sshargs, qemu.ip, testcommand))
  File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-oe-selftest/build/meta/lib/oeqa/utils/commands.py", line 191, in runCmd
    raise AssertionError("Command '%s' returned non-zero exit status %d:\n%s" % (command, result.status, exc_output))
AssertionError: Command 'ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no root@192.168.7.2 ls /etc/this-was-created-at-first-boot' returned non-zero exit status 255:
ssh: connect to host 192.168.7.2 port 22: Connection refused

Stdout:
Previous bitbake instance shutting down?, waiting to retry...
Comment 1 Ross Burton 2017-10-20 10:14:23 UTC
*** Bug 12256 has been marked as a duplicate of this bug. ***
Comment 2 Ross Burton 2017-10-20 10:14:54 UTC
The actual error is runqemu saying "Couldn't login into serial console as root using blank password".  Suggests that debug-tweaks isn't enabled?
Comment 3 Ross Burton 2017-11-06 17:38:30 UTC
Turns out I broke this test.  Working on it now.
Comment 4 Ross Burton 2017-12-21 09:45:14 UTC
Fixed in 781a1be88f5812157a231bf5771a01bb978bfcd9.