New issue
Advanced search Search tips

Issue 678024 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

provision timeout for edgar-release with chromeos4-devserver4

Project Member Reported by semenzato@chromium.org, Jan 3 2017

Issue description

This build failed:

https://uberchromegw.corp.google.com/i/chromeos/builders/edgar-release/builds/727

The bucket for the failed provision_Autoupdate.Double is here:

https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/94069833-chromeos-test/chromeos4-row12-rack8-host1/debug/

This was being served by chromeos4-devserver4.  Unfortunately that devserver is not near saturation by any measure.

https://viceroy.corp.google.com/chromeos/machines?hostname=chromeos4-devserver4&duration=5356747&utc_end=1481043176

(I also double-checked with sar.)

I think that what may have happened is some ssh glitch during the first attempt (see the "broken pipe" error below).  Then we tried again from scratch, and there wasn't enough time for two full tries.  But that suggests that each try was slower than expected.


01/02 22:25:18.128 DEBUG|        dev_server:1723| Current CrOS auto-update status: pre-setup rootfs update
01/02 22:25:28.176 DEBUG|        base_utils:0185| Running 'ssh 100.115.219.132 'curl "http://100.115.219.132:8082/get_au_status?build_name=edgar-release/R57-9146.0.0&force_update=True&pid=31197&host_name=chromeos4-row12-rack8-host1&full_update=True"''
01/02 22:25:29.501 DEBUG|        dev_server:1785| Failed to trigger auto-update process on devserver
01/02 22:25:29.502 DEBUG|        base_utils:0185| Running 'ssh 100.115.219.132 'curl "http://100.115.219.132:8082/handler_cleanup?pid=31197&host_name=chromeos4-row12-rack8-host1"''
01/02 22:25:30.847 DEBUG|        base_utils:0185| Running 'ssh 100.115.219.132 'curl "http://100.115.219.132:8082/collect_cros_au_log?pid=31197&host_name=chromeos4-row12-rack8-host1"''
01/02 22:25:32.118 DEBUG|        dev_server:1617| Saving auto-update logs into /usr/local/autotest/results/94069833-chromeos-test/autoupdate_logs/CrOS_update_chromeos4-row12-rack8-host1_31197.log
01/02 22:25:32.119 DEBUG|        dev_server:1884| Exception raised on auto_update attempt #1:
 Traceback (most recent call last):
  File "/home/chromeos-test/chromiumos/src/platform/dev/cros_update.py", line 222, in TriggerAU
    self._RootfsUpdate(chromeos_AU)
  File "/home/chromeos-test/chromiumos/src/platform/dev/cros_update.py", line 149, in _RootfsUpdate
    cros_updater.PreSetupRootfsUpdate()
  File "/home/chromeos-test/chromiumos/chromite/lib/auto_updater.py", line 904, in PreSetupRootfsUpdate
    self.device.Reboot(timeout_sec=self.REBOOT_TIMEOUT)
  File "/home/chromeos-test/chromiumos/chromite/lib/remote_access.py", line 817, in Reboot
    return self.GetAgent().RemoteReboot(timeout_sec=timeout_sec)
  File "/home/chromeos-test/chromiumos/chromite/lib/remote_access.py", line 380, in RemoteReboot
    self.RemoteSh('touch %s && reboot' % REBOOT_MARKER)
  File "/home/chromeos-test/chromiumos/chromite/lib/remote_access.py", line 340, in RemoteSh
    raise SSHConnectionError(e.result.error)
SSHConnectionError: Warning: Permanently added 'chromeos4-row12-rack8-host1,100.115.203.49' (RSA) to the list of known hosts.
Write failed: Broken pipe

 
Owner: nxia@chromium.org

Comment 2 by nxia@chromium.org, Jan 9 2017

Cc: -nxia@chromium.org dgarr...@chromium.org
Owner: xixuan@chromium.org
Looks like the timeout is expected because of SSHConnectionError. Passing to xixuan@ to look at the potential retry problem.

Comment 3 by xixuan@chromium.org, Jan 19 2017

Labels: Hotlist-Fixit

Comment 4 by xixuan@chromium.org, Jan 30 2017

Owner: ----
Labels: Hotlist-CrOS-DevServerLoad
Status: Archived (was: Untriaged)

Sign in to add a comment