provision fails because during verify, cros.verify fails because system-services isn't running |
||||||
Issue descriptionhttps://uberchromegw.corp.google.com/i/chromeos/builders/whirlwind-paladin/builds/4749 DUT successfully provisioned but during verify it failed because the system-services weren't running. This is probably a one-off but reporting for posterity. The failure was described as: "provision: FAIL: command execution error, completed successfully" * Command: /usr/bin/ssh -a -x -o ControlPath=/tmp/_autotmp_3hAiUqssh- master/socket -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o BatchMode=yes -o ConnectTimeout=30 -o ServerAliveInterval=900 -o ServerAliveCountMax=3 -o ConnectionAttempts=4 -o Protocol=2 -l root -p 22 chromeos4-row10-rack12-host2 "export LIBC_FATAL_STDERR_=1; if type \"logger\" > /dev/null 2>&1; then logger -tag \"autotest\" \"server[stack::verify|verify_software|upstart_status] -> ssh_run(status system-services | grep start/running)\";fi; status system-services | grep start/running"
,
May 28 2016
,
May 31 2016
What is system-services?
,
May 31 2016
"system-services" is the name of a standard CrOS upstart job. On Chrome OS, it starts after Chrome reaches login prompt. I don't know what triggers it on whirlwind, but if it fails to start, it's most likely a serious bug in the product code.
,
Jun 14 2016
,
Sep 21 2017
Looks like the same symptoms as https://luci-milo.appspot.com/buildbot/chromeos/peppy-paladin/16536 I also note that as pointed out in Issue 761492 , this error message is very misleading.
,
Sep 21 2017
,
Sep 26 2017
OK, the underlying flaw that causes the error is likely to be bug 765686, which I've classified as a product bug. We can/should also fix the way the problem is reported to make it easier to diagnose.
,
May 17 2018
The product issue has a separate bug and is probably fixed. Keeping this to track the poor reporting. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by kevcheng@chromium.org
, May 28 2016