During OOBE flow when checking for updates fail, connecting to valid network doesn't proceed ti Sign in screen |
|||||||||||
Issue descriptionChrome Version: 10032.4.0/ 63.0.3239.7 dev build Steps to repro: 1. The device is in Dev mode and chrome os version 10032.4.0 63.0.3239.7. 2. Prepare the machine for AU--> When on OOBE screen and Goto VT2 terminal. Prepare 'lsb-release' file for auto update. Mention as 'CHROMEOS_AUSERVER=https://omaha.sandbox.google.com/service/update2' inside lsb-release file. Document for reference: https://docs.google.com/a/google.com/document/d/1Cj_YqghbJ4j7fblYiED2YF8WYO4_2q4vMu9ZpekEFo4/edit?authkey=CLSu1ooL&hl=en_US 3. Connect to Ethernet network. 4. After EULA while device is checking for updates, disconnect ethernet network, so the update wont take place. 5. Now it comes back to OOBE screen. Now connect to 'Googleguest' network. 6. Observe that on clicking next button, it comes back to this network connect screen and doesn't proceed. Expected behavior: After connecting to valid network during OOBE flow, should be proceeded to Sign in screen Please refer the logs and video
,
Mar 2 2018
Steven any idea why this failed?
,
Mar 2 2018
There were a couple of bugs of this nature that have been fixed since 63. Since this is a subtle repro on a dev machine, I would see if we can reproduce this on 66 and if not, mark as WontFix. Otherwise this is likely an OOBE flow issue.
,
Mar 6 2018
mkarkada@ can you repro on M66?
,
Mar 6 2018
@zalcorn, I think the issue still exists. Here are the repro steps I performed on coral santa: 1. The device was in Dev mode and prepared the device for AU from CrOS version: 10443.4.0, 66.0.3356.3. 2. When on welcome screen, Goto VT2 terminal. Prepare 'lsb-release' file for auto update. 3. Connect to Ethernet network and go through OOBE. 4. At the Updating screen when downloading of updates started, I disconnected Ethernet n/w. 5. Hence display came back to network selection screen. Then connected to 'Googleguest' n/w. 6. After repeated clicking on 'Next' button, eventually proceeded to Sign in screen. Please refer the issue video. Issue video in this link: https://pantheon.corp.google.com/storage/browser/chromiumos-test-logs/bugfiles/cr/776617/On%20M66/
,
Jul 10
alemate@, stevenjb@, can you investigate?
,
Jul 11
The repro in comment #5 was for M-66, can you verify in a 68 or 69 build? A few things changed in that code semi-recently, possibly post 66 or 67.
,
Jul 12
@steven, I ran the steps in c#5 on M68 beta build (10718.50.0, 68.0.3440.59) nautilus and the behavior is still the same. On M69 dev build soraka (10866.1.0, 69.0.3486.0), after step no.5 of c#5, the display went back to 'Updating' screen. At this point downloading of updates didn't resume, but the display is stuck at this screen for a very long time (waited for >20min) and didn't proceed further. Attached screenshot for this. Attached update_engine logs for both M68 & M69.
,
Nov 12
This sounds like a pretty bad experience, can we investigate in 72?
,
Nov 13
I wonder was this also fixed with the work done in issue 873270 . Mythri to check
,
Nov 13
I ran the repro steps mentioned in c#5 as well as in the bug description; The display screen comes back to network selection screen, connected to 'Googleguest' n/w. After repeated clicking on 'Next' button, eventually proceeded to Sign in screen. Repro video for c#0: https://pantheon.corp.google.com/storage/browser/chromiumos-test-logs/bugfiles/cr/776617/On%20M72_Checking_for_updates_screen/ Repro video for c#5: https://pantheon.corp.google.com/storage/browser/chromiumos-test-logs/bugfiles/cr/776617/On%20M72_Updating_screen/
,
Nov 13
Thanks for the videos. Makes it super clear. Assigning to jennyz/ketaki since they are making changes here for 73 |
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by mkarkada@chromium.org
, Oct 20 2017