Zero-touch forces the user back into the OOBE even after it is complete |
||
Issue descriptionWhat steps will reproduce the problem? (0) rm -rf /tmp/somedir && mkdir /tmp/somedir (1) Run chrome with --login-manager --enterprise-enable-zero-touch-enrollment --user-data-dir=/tmp/somedir (2) Go through the OOBE until login, then exit. (3) Check that "OobeComplete": true is in /tmp/somedir/Local\ State (4) Run chrome with --login-manager --enterprise-enable-zero-touch-enrollment --user-data-dir=/tmp/somedir What is the expected output? The login panel should show. What do you see instead? The whole OOBE is restarted from scratch
,
Sep 16 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/ebafc22b74ceef8bb436396bf3194b8759c48a59 commit ebafc22b74ceef8bb436396bf3194b8759c48a59 Author: drcrash <drcrash@chromium.org> Date: Fri Sep 16 22:28:48 2016 Do not try to enroll past OOBE/enrollment. BUG= 647480 TEST=manual Review-Url: https://codereview.chromium.org/2340933004 Cr-Commit-Position: refs/heads/master@{#419302} [modify] https://crrev.com/ebafc22b74ceef8bb436396bf3194b8759c48a59/chrome/browser/chromeos/policy/device_cloud_policy_initializer.cc [modify] https://crrev.com/ebafc22b74ceef8bb436396bf3194b8759c48a59/chrome/browser/chromeos/policy/device_cloud_policy_initializer_unittest.cc
,
Sep 17 2016
|
||
►
Sign in to add a comment |
||
Comment 1 by drcrash@chromium.org
, Sep 15 2016