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

Issue 860758 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
OOO
Closed: Jul 6
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 0
Type: Bug



Sign in to add a comment

cyan-chrome-pfq timing out in HWTest [bvt-arc] due to provisioning hang on chromeos4-row6-rack9-host18

Project Member Reported by derat@chromium.org, Jul 6

Issue description

Two successive cyan-chrome-pfq builds have timed out in HWTest [bvt-arc] during provisioning:

http://cros-goldeneye/chromeos/healthmonitoring/suiteDetails?cidbBuildId=2725738
http://cros-goldeneye/chromeos/healthmonitoring/suiteDetails?cidbBuildId=2724728

Looking at the logs, e.g. http://stainless/browse/chromeos-autotest-results/hosts/chromeos4-row6-rack9-host18/1298963-provision/ , it looks like the DUT died:

07/05 23:33:03.983 ERROR|             utils:0286| [stderr] ssh: connect to host chromeos4-row6-rack9-host18 port 22: Connection timed out
07/05 23:33:04.993 ERROR|       autoupdater:0939| Failure preparing host prior to update.
Traceback (most recent call last):
  File "/usr/local/autotest/server/cros/autoupdater.py", line 935, in _run_update_steps
    self._prepare_host()
  File "/usr/local/autotest/server/cros/autoupdater.py", line 767, in _prepare_host
    self.host.reboot(timeout=self.host.REBOOT_TIMEOUT)
  File "/usr/local/autotest/server/hosts/cros_host.py", line 1253, in reboot
    super(CrosHost, self).reboot(**dargs)
  File "/usr/local/autotest/server/hosts/remote.py", line 164, in reboot
    self.log_op(self.OP_REBOOT, reboot)
  File "/usr/local/autotest/client/common_lib/hosts/base_classes.py", line 562, in log_op
    self.job.run_op(op, op_func, self.get_kernel_ver)
  File "/usr/local/autotest/server/server_job.py", line 950, in run_op
    op_func()
  File "/usr/local/autotest/server/hosts/remote.py", line 160, in reboot
    **dargs)
  File "/usr/local/autotest/server/hosts/remote.py", line 229, in wait_for_restart
    self.log_op(self.OP_REBOOT, op_func)
  File "/usr/local/autotest/client/common_lib/hosts/base_classes.py", line 566, in log_op
    op_func()
  File "/usr/local/autotest/server/hosts/remote.py", line 228, in op_func
    super(RemoteHost, self).wait_for_restart(timeout=timeout, **dargs)
  File "/usr/local/autotest/client/common_lib/hosts/base_classes.py", line 310, in wait_for_restart
    raise error.AutoservRebootError("Host did not return from reboot")
AutoservRebootError: Host did not return from reboot

chromeos4-row6-rack9-host18 was the DUT in question in both cases. Can it be taken out of the rotation?
 
Status: Fixed (was: Assigned)
4-6-9-18 has been moved to suites pool. File http://b/111211697 for tracking.
Cc: davidri...@chromium.org
davidriley@ said that this may be issue 639301.

Sign in to add a comment