DescriptionRevert of cros: ensure update check to complete at OOBE before allowing login (patchset #3 id:80001 of https://codereview.chromium.org/2676383002/ )
Reason for revert:
Believe this is causing a regression in linux builds
Original issue's description:
> cros: ensure update check to complete at OOBE before allowing login
>
> This CL updates the CrOS login flow to ensure the update check is
> complete at OOBE before allowing the first user to log in. Without a
> successful check for update, we can't be sure if there is a critical
> update. To play safe and avoid missing any critical update during OOBE,
> we modify the UI simply goes back to the network selection screen
> instead of proceeding to the login screen. For the non-OOBE flow, we
> don't want to block the users while failing to check for update, and
> thus preseve the existing UI behavior to proceed to the login screen.
>
> BUG=chromium:683424
> TEST=Tested the following:
> 1. Under the OOBE scenario, interrupt the network connectivity when
> the UI is checking for update. Verify that the UI goes back to the
> network selection screen.
> 2. Repeat (1) under the non-OOBE scenario. Verify that the UI proceeds
> to the login screen.
>
> Review-Url: https://codereview.chromium.org/2676383002
> Cr-Commit-Position: refs/heads/master@{#450428}
> Committed: https://chromium.googlesource.com/chromium/src/+/ec6cb24b6ad420b32f0836b8e3d4767378b90b93
TBR=benchan@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=chromium:683424
Review-Url: https://codereview.chromium.org/2699633004
Cr-Commit-Position: refs/heads/master@{#450963}
Committed: https://chromium.googlesource.com/chromium/src/+/f8969afdf8bb49522af51123fda1d2e4c5050444
Patch Set 1 #
Messages
Total messages: 9 (4 generated)
|