New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 596630 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner:
Closed: Mar 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug

Blocking:
issue 592391
issue 592401
issue 592402
issue 592410
issue 592411



Sign in to add a comment

"Failed to install device image using payload" errors in provision

Project Member Reported by steve...@chromium.org, Mar 21 2016

Issue description

There were around 36 failures on peach_pit with the following pattern:

Reason:
Failed to install device image using payload at http://172.17.40.20:8082/update/peach_pit-release/R49-7834.57.0 on chromeos4-row8-rack13-host3: command execution error.
build artifacts: https://storage.cloud.google.com/?arg=chromeos-image-archive/peach_pit-release/R49-7834.57.0.
...
ANCHOR  TestFailure{bvt-inline,provision,Failed to install device image using payload at http://172.17.40.20:8082/update/BOARD_PLACEHOLDER-release/R49-7834.57.0 on chromeos4-row8-rack13-host3: command execution error}



 
Cc: xixuan@chromium.org gwendal@chromium.org
Labels: Infra-ChromeOS
Summary: "Failed to install device image using payload" errors in provision (was: "Failed to install device image using payload" errors in bvt-inline:provision)
This has been pretty widespread across many boards: https://bugs.chromium.org/p/chromium/issues/list?can=2&q=Failed%20to%20install%20device%20image%20using%20payload%20at%20label%3Aautofiled


There seems to be two major flavors of this error:
-Failed to install device image using payload at ... SSH reports a generic error (255) which is probably a lab network failure
- Failed to install device image using payload at ... command execution error
Cc: shuqianz@chromium.org kevcheng@chromium.org
+shuqianz so she can enlighten us about these failure messages.
Erroe 1:
Failed to install device image using payload at ... SSH reports a generic error (255) which is probably a lab network failure.

It implies that we fail to ssh into the dut before running update. It could be a network flake.

Error 2:
Failed to install device image using payload at ... command execution error
It implies that update_engine fails. It is mostly because we failed to talk to the devserver or the omaha server. Just the logs of https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/tricky-tot-chrome-pfq-informational/builds/159. It failed to talk to the omaha server.
03/21 09:33:03.856 DEBUG|        base_utils:0268| [stdout] [0321/093303:ERROR:update_engine_client.cc(218)] Update failed, current operation is UPDATE_STATUS_IDLE, last error code is ErrorCode::kOmahaErrorInHTTPResponse(37)

Comment 5 by xixuan@chromium.org, Mar 28 2016

I don't turn on the SSH switch when several SSH errors happens.

cros_host:0758| Autoupdate did not complete.
03/28 05:21:37.547 ERROR|provision_AutoUpda:0138| Failed to install device image using payload at http://100.107.160.1:8082/update/edgar-release/R50-7978.34.0 on chromeos4-row12-rack7-host5. SSH reports a generic error (255) which is probably a lab network failure

Seems like not a dev_server problem, list_image_dir of dev_server has successfully finished.

Comment 6 by moch@chromium.org, Mar 31 2016

Similar provision errors seen on x86-zgb-paladin

https://uberchromegw.corp.google.com/i/chromeos/builders/x86-zgb-paladin/builds/6112

Comment 7 by za...@chromium.org, Mar 31 2016

Mergedinto: 598517
Status: Duplicate (was: Untriaged)

Comment 8 by benhenry@google.com, Apr 27 2016

Components: Infra>Client>ChromeOS
Labels: -Infra-ChromeOS

Sign in to add a comment