Issue metadata
Sign in to add a comment
|
Autoupdate failing for mysterious reasons? |
||||||||||||||||||||||||
Issue descriptionhttps://uberchromegw.corp.google.com/i/chromeos/builders/x86-alex-paladin/builds/24849 06/22 21:26:01.295 DEBUG| ssh_host:0180| Running (ssh) 'start update-engine' 06/22 21:26:01.676 DEBUG| base_utils:0278| [stdout] update-engine start/running, process 4892 06/22 21:26:01.682 DEBUG| ssh_host:0180| Running (ssh) '/usr/bin/update_engine_client -status 2>&1 | grep CURRENT_OP' 06/22 21:26:01.992 WARNI| cros_host:0755| Autoupdate did not complete. 06/22 21:26:01.999 WARNI| test:0606| Autotest caught exception when running test: Traceback (most recent call last): File "/usr/local/autotest/client/common_lib/test.py", line 600, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/usr/local/autotest/client/common_lib/test.py", line 810, in _call_test_function raise error.UnhandledTestFail(e) UnhandledTestFail: Unhandled AutoservRunError: command execution error * Command: /usr/bin/ssh -a -x -o ControlPath=/tmp/_autotmp_EpBTRossh- 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 chromeos2-row1-rack7-host7 "export LIBC_FATAL_STDERR_=1; if type \"logger\" > /dev/null 2>&1; then logger -tag \"autotest\" \"server[stack::run_update|reset_update_engine|check_update_status] -> ssh_run(/usr/bin/update_engine_client -status 2>&1 | grep CURRENT_OP)\";fi; /usr/bin/update_engine_client -status 2>&1 | grep CURRENT_OP" Exit status: 1 Duration: 0.251242160797 How do we debug this?
,
Jun 28 2016
,
Jun 28 2016
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by autumn@chromium.org
, Jun 28 2016