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

Issue 790561 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Dec 2017
Cc:
drinkcat@chromium.org
xixuan@chromium.org
█ slavamn@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

RootfsUpdateError: Build stumpy-paladin/R64-10173.0.0-rc3 failed to boot on chromeos4-row2-rack9-host7; system rolled back to previous build

Project Member Reported by athilenius@chromium.org, Nov 30 2017 
Seeing the failure (https://logs.chromium.org/v/?s=chromeos%2Fbb%2Fchromeos%2Fstumpy-paladin%2F30417%2F%2B%2Frecipes%2Fsteps%2FHWTest__provision_%2F0%2Fstdout):

provision     FAIL: Unhandled DevServerException: CrOS auto-update failed for host chromeos4-row2-rack9-host7: 0) RootfsUpdateError: Build stumpy-paladin/R64-10173.0.0-rc3 failed to boot on chromeos4-row2-rack9-host7; system rolled back to previous build, 1) RootfsUpdateError: Build stumpy-paladin/R64-10173.0.0-rc3 failed to boot on 100.115.193.37; system rolled back to previous build, 
provision   [ FAILED ]
provision     FAIL: Unhandled DevServerException: CrOS auto-update failed for host chromeos4-row2-rack9-host4: 0) ChromiumOSUpdateError: chromeos4-row2-rack9-host4 cannot recover from reboot at post check of rootfs update, 1) SSHConnectionError: ssh: connect to host 100.115.193.34 port 22: Connection timed out, 
provision   [ FAILED ]

In stumpy-paladin build: https://uberchromegw.corp.google.com/i/chromeos/builders/stumpy-paladin/builds/30417

Comment 1 by slavamn@chromium.org, Dec 2 2017 

Looking at https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/159534932-chromeos-test/chromeos4-row2-rack9-host5

2017/11/30 10:34:29.070 DEBUG|    cros_build_lib:0593| 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-tmpi1q8V0/testing_rsa root@100.115.193.35 -- rm -rf /mnt/stateful_partition/unencrypted/preserve/cros-update/tmp.SDEixSz3p4
2017/11/30 10:34:29.262 DEBUG|       cros_update:0339| Error happens in CrOS auto-update: RootfsUpdateError('Build stumpy-paladin/R64-10173.0.0-rc3 failed to boot on 100.115.193.35; system rolled back to previous build',)

It happens after several checks for the machine after update are done. The build seems to be up and healthy. It seems either 'rm' took too long, or ssh connection got lost.

Comment 2 by xixuan@chromium.org, Dec 2 2017

Status: WontFix (was: Untriaged)
Sorry, missing this bug. The stumpy-paladin fails due to bad CL: https://chromium-review.googlesource.com/c/chromiumos/platform2/+/794990
►

Sign in to add a comment