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

Issue 716543 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Closed: May 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Moblab setup will not accept boto key

Project Member Reported by haddowk@chromium.org, Apr 28 2017

Issue description

when setting up boto key for the 

gs://chromeos-moblab-haddowktest/

bucket I get 

Error:The boto access key is not valid despite checking the settings several times.
 
From the logs run suite is crashing

04/28 02:52:44.659 DEBUG|        base_utils:0185| Running 'rsync -L  --timeout=1800 --rsh='/usr/bin/ssh -a -x    -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' -az --no-o --no-g root@chromeos2-row2-rack8-host7:"/usr/local/autotest/logs" "/usr/local/autotest/results/114461536-chromeos-test/moblab_RunSuite/results/moblab_logs"'
04/28 02:52:45.830 DEBUG|              test:0389| Test failed due to command execution error
* Command: 
    /usr/bin/ssh -a -x     -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 chromeos2-row2-rack8-host7 "export
    LIBC_FATAL_STDERR_=1; if type \"logger\" > /dev/null 2>&1; then logger
    -tag \"autotest\" \"server[stack::_call_run_once|run_once|run_as_moblab]
    -> ssh_run(su - moblab -c '/usr/local/autotest/site_utils/run_suite.py
    --pool='' --board=cyan --build=cyan-release/R55-8872.67.0
    --suite_name=smoke')\";fi; su - moblab -c
    '/usr/local/autotest/site_utils/run_suite.py --pool='' --board=cyan
    --build=cyan-release/R55-8872.67.0 --suite_name=smoke'"
Exit status: 255
Duration: 3646.11512089

stdout:
[?25h[?0c
stderr:
ERROR:root:Could not import tzlocal.
Autotest instance: localhost
04-28-2017 [01:51:45] Submitted create_suite_job rpc
04-28-2017 [01:51:53] Created suite job: http://localhost/afe/#tab_id=view_job&object_id=1
@@@STEP_LINK@Link to suite@http://localhost/afe/#tab_id=view_job&object_id=1@@@
The suite job has another 23:29:58.881610 till timeout.
04-28-2017 [02:36:29] Suite job is finished.
04-28-2017 [02:36:29] Start collectint test results and dump them to json.
Write failed: Broken pipe. Exception log follows the after_iteration_hooks.
04/28 02:52:45.831 DEBUG|              test:0392| starting after_iteration_hooks
Cc: stephenlin@chromium.org ayatane@chromium.org
Adding 	ayatane@chromium.org since the CL's related to suite refactor look the most suspicious.  Any insight as to why run_suite might be crashing on moblab 59 ?
It looks like the suite job finished normally.  The test result collection failed

04-28-2017 [02:36:29] Suite job is finished.
04-28-2017 [02:36:29] Start collectint test results and dump them to json.
Write failed: Broken pipe. Exception log follows the after_iteration_hooks.

Or rather, wherever the JSON output was being written was closed.
Owner: haddowk@chromium.org
Cc: -ayatane@chromium.org
Moved info to https://bugs.chromium.org/p/chromium/issues/detail?id=716215

I mixed up the bugs I am working on
Status: Fixed (was: Assigned)

Comment 7 by dchan@chromium.org, Jan 22 2018

Status: Archived (was: Fixed)

Sign in to add a comment