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

Issue 654330 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

CrOS Auto-Update Failure: rootfs update failure

Project Member Reported by kevcheng@chromium.org, Oct 10 2016

Issue description

DUT: chromeos4-row10-jetstream-host6
Failed Build: https://uberchromegw.corp.google.com/i/chromeos/builders/whirlwind-paladin/builds/5990

Not exactly sure what failed...

2016/10/09 17:36:22.306 INFO |      auto_updater:0457| Waiting for update...status: UPDATE_STATUS_DOWNLOADING at progress 0.807968
2016/10/09 17:36:32.308 DEBUG|    cros_build_lib:0565| RunCommand: 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-tmp3ZNxiJ/testing_rsa root@100.115.219.28 -- update_engine_client --status
2016/10/09 17:36:57.654 ERROR|      auto_updater:0479| Rootfs update failed.
...
...
...
2016/10/09 17:38:15.910 DEBUG|       cros_update:0224| Error happens in CrOS auto-update: RootfsUpdateError('Failed to perform rootfs update: RunCommandError("cwd=None, extra env={\'LC_MESSAGES\': \'C\'}", <chromite.lib.cros_build_lib.CommandResult object at 0x7f50c1028dd0>, None)',)
 

Comment 1 by xixuan@chromium.org, Oct 10 2016

Summary: CrOS Auto-Update Failure: rootfs update failure (was: CrOS Auto-Update Failure: RunCommandError(...))
Status: WontFix (was: Untriaged)
Feels it's two cases of a type of provision failure. Mark won't fix for now. If it happens again and again, let's open a long-term bug for tracking it.

Sign in to add a comment