Servo USB repair fails with 'The host has wrong cros-version label.'
Reported by
jrbarnette@chromium.org,
Apr 28 2016
|
|||
Issue description
After repair re-installs the stable test image on a DUT,
re-verify can fail with the message 'The host has wrong
cros-version label.' A sample is below:
$ dut-status -g -u '2016-04-28 07:15:00' chromeos4-row3-rack8-host2
chromeos4-row3-rack8-host2
2016-04-28 07:01:12 OK http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos4-row3-rack8-host2/38355-verify/
2016-04-28 06:40:03 NO http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos4-row3-rack8-host2/38310-repair/
The failed repair job includes this:
START ---- repair.usb timestamp=1461851000 localtime=Apr 28 06:43:20
GOOD ---- verify.ssh timestamp=1461851965 localtime=Apr 28 06:59:25
GOOD ---- verify.writable timestamp=1461851965 localtime=Apr 28 06:59:25
GOOD ---- verify.tpm timestamp=1461851965 localtime=Apr 28 06:59:25
GOOD ---- verify.good_au timestamp=1461851965 localtime=Apr 28 06:59:25
GOOD ---- verify.python timestamp=1461851966 localtime=Apr 28 06:59:26
FAIL ---- verify.cros timestamp=1461851968 localtime=Apr 28 06:59:28 The host has wrong cros-version label.
END FAIL ---- repair.usb timestamp=1461851968 localtime=Apr 28 06:59:28
,
May 4 2017
This issue has been available for more than 365 days, and should be re-evaluated. Please re-triage this issue. The Hotlist-Recharge-Cold label is applied for tracking purposes, and should not be removed after re-triaging the issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 14 2018
This bug is very old, is Untriaged, and has no owner. If it is still relevant, reopen as Untriaged or open a new bug |
|||
►
Sign in to add a comment |
|||
Comment 1 by autumn@chromium.org
, May 3 2016