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

Issue 653037 link

Starred by 1 user
Status: Duplicate
Owner:
xixuan@chromium.org
Closed: Dec 2016
Cc:
█ mcchou@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

test_that provisioning fails against locked DUT in lab

Project Member Reported by mcchou@chromium.org, Oct 5 2016 
In order to get rid of the question marks on using a different build name to run the test, I setup and built veyron_minnie locally. And I can still repro the issue. 

Device:
  veyron_minnie
Command:
  test_that -b veyron_minnie -i trybot-veyron_minnie-paladin/R55-8847.0.0-b1544 android1758-row4-rack8-host3.cros suite:bluetooth
Repro rate:
  100%
Observation:
  The image update never completes, so the following tests cannot be executed.
Log:
  Please see test_that_result.tar.gz for the test_that logs.
test_that_result.tar.gz
12.9 MB Download

Comment 1 by akes...@chromium.org, Oct 6 2016

Owner: xixuan@chromium.org
Summary: test_that provisioning fails against locked DUT in lab (was: provisioning investigation)
There seems to be something strange going on when using 'test_that' against a locked DUT in the lab. It seems to be trying to follow the new style provision flow, but failing.

xixuan@ could you take a look at these logs and see if you can determine why it's failing?

Comment 2 by xixuan@chromium.org, Oct 6 2016 

Based on these error msg:

10/05 04:17:29.160 ERROR|        base_utils:0280| [stderr] [1005/021728:INFO:update_engine_client.cc(447)] Forcing an update by setting app_version to ForcedUpdate.
10/05 04:17:29.161 ERROR|        base_utils:0280| [stderr] [1005/021728:INFO:update_engine_client.cc(449)] Initiating update check and install.
10/05 04:17:29.162 ERROR|        base_utils:0280| [stderr] [1005/021728:INFO:update_engine_client.cc(478)] Waiting for update to complete.
10/05 04:17:41.226 ERROR|        base_utils:0280| [stderr] [1005/021740:ERROR:update_engine_client.cc(217)] Update failed, current operation is UPDATE_STATUS_IDLE, last error code is ErrorCode::kOmahaErrorInHTTPResponse(37)
10/05 04:17:41.368 ERROR|       autoupdater:0179| command execution error
* Command: 
    /usr/bin/ssh -a -x    -o ControlPath=/tmp/_autotmp_r__8lsssh-
    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
    android1758-row4-rack8-host3.cros "export LIBC_FATAL_STDERR_=1; if type
    \"logger\" > /dev/null 2>&1; then logger -tag \"autotest\"
    \"server[stack::update_rootfs|update_image|_base_update_handler] ->
    ssh_run(/usr/bin/update_engine_client --update
    --omaha_url=http://100.115.219.132:8082/update/trybot-veyron_minnie-
    paladin/R55-8847.0.0-b1544)\";fi; /usr/bin/update_engine_client --update
    --omaha_url=http://100.115.219.132:8082/update/trybot-veyron_minnie-
    paladin/R55-8847.0.0-b1544"
Exit status: 1
Duration: 12.6571490765

It's not using the new provision code flow. And old provision framework sometimes has this kind of error: "ErrorCode::kOmahaErrorInHTTPResponse(37)"

Comment 3 by autumn@chromium.org, Oct 11 2016

Labels: -current-issue

Comment 4 by xixuan@chromium.org, Dec 9 2016

Mergedinto: 657548
Status: Duplicate (was: Assigned)
►

Sign in to add a comment