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

Issue 751381 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Enguarde failing autoupdate with RootfsUpdateError('Update failed with unexpected update status: UPDATE_STATUS_IDLE',)

Project Member Reported by dhadd...@chromium.org, Aug 2 2017

Issue description

https://wmatrix.googleplex.com/platform/paygen_au_canary?platforms=enguarde

Unhandled DevServerException: CrOS auto-update failed for host chromeos4-row10-rack2-host19: RootfsUpdateError: Failed to perform rootfs update: RootfsUpdateError('Update failed with unexpected update status: UPDATE_STATUS_IDLE',)

This error message just means that something went wrong in update_engine and we can't continue
 
Summary: Enguarde failing autoupdate with RootfsUpdateError('Update failed with unexpected update status: UPDATE_STATUS_IDLE',) (was: Enguarde failing autoupdate with )
Update engine log failure

[0801/134020:INFO:action_processor.cc(116)] ActionProcessor: finished DownloadAction with code ErrorCode::kSuccess
[0801/134020:INFO:action_processor.cc(143)] ActionProcessor: starting OmahaRequestAction
[0801/134020:INFO:omaha_request_action.cc(680)] Posting an Omaha request to http://127.0.0.1:37627/update/pregenerated
[0801/134020:INFO:omaha_request_action.cc(681)] Request: <?xml version="1.0" encoding="UTF-8"?>
<request protocol="3.0" version="ChromeOSUpdateEngine-0.1.0.0" updaterversion="ChromeOSUpdateEngine-0.1.0.0" installsource="ondemandupdate" ismachine="1">
    <os version="Indy" platform="Chrome OS" sp="9798.0.0_x86_64"></os>
    <app appid="{BB86912A-29BE-A59B-31EF-8F4DD1C023E2}" version="9798.0.0" track="stable-channel" lang="en-US" board="enguarde" hardware_class="ENGUARDE A2A-A4K-E6A-A6O" delta_okay="true" fw_version="" ec_version="" installdate="3864" >
        <event eventtype="14" eventresult="1"></event>
    </app>
</request>

[0801/134020:ERROR:utils.cc(88)] AddDBusError(...): Domain=dbus, Code=org.freedesktop.DBus.Error.ServiceUnknown, Message=The name org.chromium.NetworkProxyService was not provided by any .service files
[0801/134020:WARNING:chrome_browser_proxy_resolver.cc(121)] Failed to resolve proxy: The name org.chromium.NetworkProxyService was not provided by any .service files
[0801/134020:INFO:libcurl_http_fetcher.cc(146)] Starting/Resuming transfer
[0801/134020:INFO:libcurl_http_fetcher.cc(165)] Using proxy: no
[0801/134020:INFO:libcurl_http_fetcher.cc(286)] Not setting http(s) curl options because we are running a dev/test image
[0801/134020:INFO:libcurl_http_fetcher.cc(433)] HTTP response code: 200
[0801/134020:INFO:libcurl_http_fetcher.cc(509)] Transfer completed (200), 253 bytes downloaded
[0801/134020:INFO:omaha_request_action.cc(940)] Omaha request response: <?xml version="1.0" encoding="UTF-8"?>
  <response protocol="3.0">
    <daystart elapsed_seconds="49220"/>
    <app appid="{87efface-864d-49a5-9bb3-4b050a7c227a}" status="ok">
      <ping status="ok"/>
      <event status="ok"/>
    </app>
  </response>
[0801/134020:INFO:action_processor.cc(116)] ActionProcessor: finished OmahaRequestAction with code ErrorCode::kSuccess
[0801/134020:INFO:action_processor.cc(143)] ActionProcessor: starting FilesystemVerifierAction
[0801/134020:INFO:filesystem_verifier_action.cc(111)] Hashing partition 0 (system) on device /dev/mmcblk0p3
[0801/134314:ERROR:file_stream.cc(461)] ReadNonBlocking(...): Domain=system, Code=EIO, Message=Input/output error
[0801/134314:ERROR:filesystem_verifier_action.cc(154)] Unable to schedule an asynchronous read from the stream.
[0801/134314:INFO:prefs.cc(122)] delta-update-failures not present in /var/lib/update_engine/prefs
[0801/134314:INFO:action_processor.cc(116)] ActionProcessor: finished FilesystemVerifierAction with code ErrorCode::kError
[0801/134314:INFO:action_processor.cc(121)] ActionProcessor: Aborting processing due to failure.
[0801/134314:INFO:update_attempter.cc(881)] Processing Done.
[0801/134314:INFO:cpu_limiter.cc(71)] Setting cgroup cpu shares to  1024
[0801/134314:INFO:cpu_limiter.cc(79)] CPU shares = 1024
[0801/134314:ERROR:update_attempter.cc(1277)] Update failed.
[0801/134314:INFO:payload_state.cc(248)] Updating payload state for error code: 47 (ErrorCode::kFilesystemVerifierError)

Cc: ahass...@chromium.org
The versions we were updating from and to were different. But the DUT was the same: chromeos4-row10-rack2-host19


Cc: jkwang@chromium.org
+jkwang@ showed me similar error. To me it looks like UE could not read from /dev/mmcblk0p3. Could any changes in kernel or changes related to hdd firmware cause this? There has been no changes in UE recently that could have caused this.

Comment 4 by jkwang@google.com, Aug 2 2017

Cc: shuqianz@chromium.org
Well.. as it's the same DUT. Would there be something wrong with the DUT setup?
Status: WontFix (was: Untriaged)
This is no longer an issue 

Sign in to add a comment