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

Issue 746583 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Jul 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Bob paygen_au* failures: RootfsUpdateError: After update and reboot, Chrome failed to reach login screen within 120 seconds

Project Member Reported by dhadd...@chromium.org, Jul 19 2017

Issue description

Investigate these failures 
 
Summary: paygen_au* failures: RootfsUpdateError: After update and reboot, Chrome failed to reach login screen within 120 seconds (was: paygen_au* failures on bob: RootfsUpdateError: After update and reboot, Chrome failed to reach login screen within 120 seconds)
Seeing on bob and lumpy on paygen_au_canary runs 
Cc: abod...@chromium.org mkarkada@chromium.org dhadd...@chromium.org sdantul...@chromium.org josa...@chromium.org
Owner: keta...@chromium.org
This is a real failure. Bob gets stuck on the sign in screen on the build it is currently serving on canary: 9608.0.0

So when the AU test puts on that build it gets stuck on the sign in screen and times out.

It seems like it has been serving this build for ages now and not updated with the rest of the boards:
https://cros-goldeneye.corp.google.com/chromeos/console/listOmaha

Over to Ketaki
Status: Assigned (was: Untriaged)
Cc: kathrelk...@chromium.org
+milestone owner
Summary: Bob paygen_au* failures: RootfsUpdateError: After update and reboot, Chrome failed to reach login screen within 120 seconds (was: paygen_au* failures: RootfsUpdateError: After update and reboot, Chrome failed to reach login screen within 120 seconds)
Status: Fixed (was: Assigned)
Status: Verified (was: Fixed)

Sign in to add a comment