chromeos4-row1-rack3-host11 in a bad state |
|
Issue descriptionOriginally, I thought this was the same as https://crbug.com/753189 , but I'm told it's not. This DUT appears to be failing provision regularly, but passing repair. I don't understand why.
,
Aug 16 2017
08/07 17:16:53.112 DEBUG| utils:0212| Running 'ssh 100.115.219.136 'curl "http://100.115.219.136:8082/kill_au_proc?pid=28241&host_name=100.115.192.17"''
08/07 17:16:54.814 DEBUG| dev_server:2149| Exception raised on auto_update attempt #2:
Traceback (most recent call last):
File "/home/chromeos-test/chromiumos/src/platform/dev/cros_update.py", line 219, in TriggerAU
version_match = chromeos_AU.PreSetupCrOSUpdate()
File "/home/chromeos-test/chromiumos/chromite/lib/auto_updater.py", line 1214, in PreSetupCrOSUpdate
**self._cmd_kwargs)
File "/home/chromeos-test/chromiumos/chromite/lib/auto_updater.py", line 1171, in _RetryCommand
cmd, delay_sec=DELAY_SEC_FOR_RETRY, **kwargs)
File "/home/chromeos-test/chromiumos/chromite/lib/retry_util.py", line 271, in RetryException
return _run()
File "/home/chromeos-test/chromiumos/chromite/lib/retry_util.py", line 176, in _Wrapper
ret = func(*args, **kwargs)
File "/home/chromeos-test/chromiumos/chromite/lib/retry_util.py", line 270, in _run
return functor(*args, **kwargs)
File "/home/chromeos-test/chromiumos/chromite/lib/remote_access.py", line 1098, in RunCommand
return super(ChromiumOSDevice, self).RunCommand(cmd, **kwargs)
File "/home/chromeos-test/chromiumos/chromite/lib/remote_access.py", line 942, in RunCommand
return self.BaseRunCommand(cmd, **kwargs)
File "/home/chromeos-test/chromiumos/chromite/lib/remote_access.py", line 889, in BaseRunCommand
return self.GetAgent().RemoteSh(cmd, **kwargs)
File "/home/chromeos-test/chromiumos/chromite/lib/remote_access.py", line 337, in RemoteSh
return cros_build_lib.RunCommand(ssh_cmd, **kwargs)
File "/home/chromeos-test/chromiumos/chromite/lib/cros_build_lib.py", line 645, in RunCommand
raise RunCommandError(msg, cmd_result)
RunCommandError: return code: 1; command: ssh -p 22 '-oConnectionAttempts=4' '-oUserKnownHostsFile=/dev/null' '-oProtocol=2' '-oConnectTimeout=30' '-oServerAliveCountMax=3' '-oStrictHostKeyChecking=no' '-oServerAliveInterval=10' '-oNumberOfPasswordPrompts=0' '-oIdentitiesOnly=yes' -i /tmp/ssh-tmpPlhzn_/testing_rsa root@100.115.192.17 -- touch /var/tmp/provision_failed
cmd=['ssh', '-p', '22', '-oConnectionAttempts=4', '-oUserKnownHostsFile=/dev/null', '-oProtocol=2', '-oConnectTimeout=30', '-oServerAliveCountMax=3', '-oStrictHostKeyChecking=no', '-oServerAliveInterval=10', '-oNumberOfPasswordPrompts=0', '-oIdentitiesOnly=yes', '-i', '/tmp/ssh-tmpPlhzn_/testing_rsa', 'root@100.115.192.17', '--', 'touch', '/var/tmp/provision_failed'], extra env={'LC_MESSAGES': 'C'}
auto_updater failed at ssh. dgarrett@ already locked the dut and the dut is already in suite pool. I'll file a ticket to the lab to fix this dut.
,
Aug 16 2017
|
|
►
Sign in to add a comment |
|
Comment 1 by dgarr...@chromium.org
, Aug 16 2017