Issue metadata
Sign in to add a comment
|
Chrome OS device loses enterprise enrollment policy, single app kiosk
Reported by
josh@arreya.com,
Apr 19 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 9202.64.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.146 Safari/537.36 Platform: 9202.64.0 (Official Build) stable-channel panther Steps to reproduce the problem: 1. Set up Chromebox from out of box, allow to auto update 2. Ctrl-Alt-E on login screen and input enterprise enrollment credentials. 3. Kiosk app starts and runs normally 4. Verify device is enrolled in Google Admin console, Device Management 5. After an unknown combination of time, power cycles and network connects/disconnects, device will reboot and no longer start the kiosk app. What is the expected behavior? After power event and/or network event, device should return to kiosk app set in device policy and not return to the Chrome desktop What went wrong? Device appears to have been "wiped" and reboots as if the device was "out of the box". If "force enroll device on wipe" policy setting is set for the Organizational Unit (OU), the device will prompt the user to input enterprise enrollment credentials after selecting a network and accepting Terms of Service. Device no longer shows in admin console as "Online". Behavior typically occurs on devices set up before shipping to clients. Once the client receives the device, it appears as if the device has not been configured for single app kiosk mode. 5 ASUS Chromebox CN60s in the same physical location (same power and network environment) experienced same failure after extended network loss and power cycles. 3 or more of the same model Chromeboxes have experienced similar behavior in unique locations. Issue occurs on multiple enrollment domains. Did this work before? Yes Chrome version: 57.0.2987.137 Channel: stable OS Version: 9202.64.0 Flash Version: Shockwave Flash 25.0 r0
,
Apr 19 2017
Can you please upload device logs after the issues happens? It looks like it is related to - https://bugs.chromium.org/p/chromium/issues/detail?id=693439
,
Apr 19 2017
Log attached. This is off a device enrolled before shipping to customer, arrived "wiped" and prompted the user to enterprise enroll the device.
,
Apr 19 2017
Log of similar issue on device that was updated from 53 -> 57, has similar entry to linked issue https://bugs.chromium.org/p/chromium/issues/detail?id=693439. Possibly related 2017/04/19 15:09:24 UTC Self-repair incoherent stateful partition: var and home. History: /home/chronos /var /home 2017/04/19 15:09:24 UTC (preserve log): /sbin/clobber-state fast keepimg 2017/04/19 15:09:26 UTC (restore log): /sbin/clobber-state
,
Apr 19 2017
Additional log from device in same environment as comment #3 above. Device also displayed same behavior.
,
Apr 20 2017
,
Apr 25 2017
Assigning to Raj to triage
,
May 16 2017
Another enterprise customer is affected. - The issue occurred around April 24 (JST) on 1 devices. - Re-enrollment was necessary after the affected devies are resetted. [Affected devices] Asus Chromebox CN62 Google Chrome Version 56.0.2924.121 Platform Version 9000.97.0 (Official Build) stable-channel guado Firmware Version Google_Guado.6301.108.4 Domain, Affected device S/N,Support Case# https://drive.google.com/open?id=1M8d3wvrLZyeTy7XlrxReYDlswu1TiJD7EN6GZAITGDI clobber.log shows 2017/04/24 06:53:09 UTC (repair): /dev/sda1 Self-repair corrupted stateful partition eventlog.txt 0 | 2017-04-24 15:53:06 | SUS Power Fail 1 | 2017-04-24 15:53:06 | System Reset 2 | 2017-04-24 15:53:06 | ACPI Wake | S5 3 | 2017-04-24 15:53:06 | Wake Source | Power Button | 0 4 | 2017-04-24 15:54:17 | Kernel Event | Clean Shutdown Debug log tgz https://drive.google.com/open?id=0B01ZVp8vDQocSHpSUWNvMmNGMTg Clobber, eventlog & message log already extracted here: https://drive.google.com/open?id=0B01ZVp8vDQocSWJPNV9wOV9pNTg
,
May 17 2017
Judging from clobber.log output: - #c4 does look similar to crbug.com/693439. I am dup'ing this bug to crbug.com/693439 to consolidate information. - #c9 looks more like crbug.com/711821. I am copying the info to crbug.com/711821. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by kathrelk...@chromium.org
, Apr 19 2017Components: UI>Shell>Kiosk