Issue 243909 in chromium: update engine not updating when a build is properly staged on the devserver

[chro...@googlecode.com]

Status: Available
Owner: ----
CC: garn...@chromium.org
Labels: Type-Bug Pri-2 Hardware-Lab OS-Chrome

New issue 243909 by dennis...@chromium.org: update engine not updating
when a build is properly staged on the devserver
http://code.google.com/p/chromium/issues/detail?id=243909

As part of this issue:
https://code.google.com/p/chromium/issues/detail?id=243790

A problem was observed where update engine failed to update a DUT even
though the updated build was properly staged on the devserver.

https://storage.cloud.google.com/?arg=chromeos-autotest-results/3088158-chromeos-test/chromeos2-row2-rack4-host7

From the logs in the above directory, autoserv.DEBUG shows this:


05/24 09:44:54.026 DEBUG|base_utils:0119| [stdout]
[0524/094342:ERROR:update_engine_client.cc(248)] Update failed.
05/24 09:44:54.026 DEBUG|base_utils:0119| [stdout] LAST_CHECKED_TIME=0
05/24 09:44:54.027 DEBUG|base_utils:0119| [stdout] PROGRESS=0.000000
05/24 09:44:54.027 DEBUG|base_utils:0119| [stdout]
CURRENT_OP=UPDATE_STATUS_CHECKING_FOR_UPDATE
05/24 09:44:54.027 DEBUG|base_utils:0119| [stdout] NEW_VERSION=0.0.0.0
05/24 09:44:54.027 DEBUG|base_utils:0119| [stdout] NEW_SIZE=0
05/24 09:44:54.027 DEBUG|base_utils:0119| [stdout] LAST_CHECKED_TIME=0
05/24 09:44:54.027 DEBUG|base_utils:0119| [stdout] PROGRESS=0.000000
05/24 09:44:54.027 DEBUG|base_utils:0119| [stdout]
CURRENT_OP=UPDATE_STATUS_CHECKING_FOR_UPDATE
05/24 09:44:54.027 DEBUG|base_utils:0119| [stdout] NEW_VERSION=0.0.0.0
05/24 09:44:54.028 DEBUG|base_utils:0119| [stdout] NEW_SIZE=0
05/24 09:44:54.028 DEBUG|base_utils:0119| [stdout] LAST_CHECKED_TIME=0
05/24 09:44:54.028 DEBUG|base_utils:0119| [stdout] PROGRESS=0.000000
05/24 09:44:54.028 DEBUG|base_utils:0119| [stdout]
CURRENT_OP=UPDATE_STATUS_CHECKING_FOR_UPDATE
05/24 09:44:54.028 DEBUG|base_utils:0119| [stdout] NEW_VERSION=0.0.0.0
05/24 09:44:54.028 DEBUG|base_utils:0119| [stdout] NEW_SIZE=0
05/24 09:44:54.028 DEBUG|base_utils:0119| [stdout] LAST_CHECKED_TIME=0
05/24 09:44:54.028 DEBUG|base_utils:0119| [stdout] PROGRESS=0.000000
05/24 09:44:54.029 DEBUG|base_utils:0119| [stdout]
CURRENT_OP=UPDATE_STATUS_IDLE
05/24 09:44:54.029 DEBUG|base_utils:0119| [stdout] NEW_VERSION=0.0.0.0
05/24 09:44:54.029 DEBUG|base_utils:0119| [stdout] NEW_SIZE=0
05/24 09:44:54.031 ERROR| process:0274| Process Process-1:
05/24 09:44:54.031 ERROR| traceback:0013| Traceback (most recent call last):
05/24 09:44:54.032 ERROR| traceback:0013|
File "/usr/lib/python2.7/multiprocessing/process.py", line 258, in
_bootstrap
05/24 09:44:54.032 ERROR| traceback:0013| self.run()
05/24 09:44:54.033 ERROR| traceback:0013|
File "/usr/lib/python2.7/multiprocessing/process.py", line 114, in run
05/24 09:44:54.033 ERROR| traceback:0013| self._target(*self._args,
**self._kwargs)
05/24 09:44:54.034 ERROR| traceback:0013|
File "/usr/local/autotest/client/common_lib/cros/autoupdater.py", line 239,
in _update_root
05/24 09:44:54.034 ERROR| traceback:0013| raise update_error
05/24 09:44:54.035 ERROR| traceback:0013| RootFSUpdateError: update-engine
failed on chromeos2-row2-rack4-host7


And the most recent log under the sysinfo/update_engine directory shows
this near the bottom:

[0524/094341:INFO:omaha_request_action.cc(691)] Omaha request response:
<?xml version="1.0" encoding="UTF-8"?>
<response protocol="3.0">
<daystart elapsed_seconds="35055"/>
<app appid="{87efface-864d-49a5-9bb3-4b050a7c227a}" status="ok">
<ping status="ok"/>
<updatecheck status="noupdate"/>
</app>
</response>


So update_engine reports that there's nothing to update, but it was
verified that the build was actually staged on the devserver.

We need to figure out why the update did not occur as expected.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Comment #5 on issue 243909 by dennis...@chromium.org: update engine not

updating when a build is properly staged on the devserver
http://code.google.com/p/chromium/issues/detail?id=243909

We've locked one of the borked DUTs in case it helps for investigation:
chromeos2-row2-rack5-host12

[chro...@googlecode.com]

Updates:
Status: WontFix

Comment #6 on issue 243909 by so...@chromium.org: update engine not updating

when a build is properly staged on the devserver
http://code.google.com/p/chromium/issues/detail?id=243909

This is due to a bug present in Patch Set 5 which re-imaged this machine to
a machine that had a bad update engine
(https://gerrit.chromium.org/gerrit/#/c/55805/). Please unlock/recover the
machine.