Chrome version: 58-61
OS version: 58-61
Case#: 13902894

Description:
Crashes ID 
Uploaded Crash Report ID e7b702fa9ff6927f 
Uploaded Crash Report ID b8b4accb46dfe4bd 
Uploaded Crash Report ID 3cd898870d4a5eba 
Uploaded Crash Report ID de2b08c4658e3cad 
Uploaded Crash Report ID 3dfc6d00fa0617ee 
Uploaded Crash Report ID 8da97384e29cce2d 
Uploaded Crash Report ID 89d7c6a8f8edeaf7 
Uploaded Crash Report ID 15c836f4d007a603 
Uploaded Crash Report ID fa35f2ec1bda4f2b 
Uploaded Crash Report ID 88c7ca09ae1d2624 
Uploaded Crash Report ID 429cb293a068f254 

- Issue description: 
-Customer called in because the devices were crashing when they were enrolled, after 
the enrollment they would start to crash, they go off and get stuck 
-Devices are in version 58, we wiped one device, did not enrolled it and then we updated it 
-Now the devices in stable but it is working the same way 
-Tested the Crosh Network_diag --hosts and it passed in one device 
-Shared the Set up a hostname whitelist article for him to whitelist the URLs 
-Advise to test in a different network and will advise to check if he has any proxy setting 
-The SN that we have been testing are 
6C27000624 
1S20GE0003USLR08NEBG 
1S20GE0003USLR08NE4G 
-Customer will whitelist and update after that 


Steps to reproduce: 
N/A

Current Behavior / Reproduction: 

Expected Behavior: 
-Devices should work normally after they have been enrolled 
-The devices get stuck, or go off for a few seconds and it is unresponsive to any command 

Drive link to logs: 
https://drive.google.com/open?id=1yw0z_j3BNuY_yHRTXBl9mCU1qeqaIJb9
https://drive.google.com/open?id=1l8Eey9iF7ht6LMKrn3O915KG74b4aZbf

 

Chrome version: 58-61
OS version: 58-61
Case#: 13902894

Description:
Crashes ID 
Uploaded Crash Report ID e7b702fa9ff6927f 
Uploaded Crash Report ID b8b4accb46dfe4bd 
Uploaded Crash Report ID 3cd898870d4a5eba 
Uploaded Crash Report ID de2b08c4658e3cad 
Uploaded Crash Report ID 3dfc6d00fa0617ee 
Uploaded Crash Report ID 8da97384e29cce2d 
Uploaded Crash Report ID 89d7c6a8f8edeaf7 
Uploaded Crash Report ID 15c836f4d007a603 
Uploaded Crash Report ID fa35f2ec1bda4f2b 
Uploaded Crash Report ID 88c7ca09ae1d2624 
Uploaded Crash Report ID 429cb293a068f254 

- Issue description: 
-Customer called in because the devices were crashing when they were enrolled, after 
the enrollment they would start to crash, they go off and get stuck 
-Devices are in version 58, we wiped one device, did not enrolled it and then we updated it 
-Now the devices in stable but it is working the same way 
-Tested the Crosh Network_diag --hosts and it passed in one device 
-Shared the Set up a hostname whitelist article for him to whitelist the URLs 
-Advise to test in a different network and will advise to check if he has any proxy setting 
-The SN that we have been testing are 
6C27000624 
1S20GE0003USLR08NEBG 
1S20GE0003USLR08NE4G 
-Customer will whitelist and update after that 


Steps to reproduce: 
N/A

Current Behavior / Reproduction: 
-The devices get stuck, or go off for a few seconds and it is unresponsive to any command 

Expected Behavior: 
-Devices should work normally after they have been enrolled 

Drive link to logs: 
https://drive.google.com/open?id=1yw0z_j3BNuY_yHRTXBl9mCU1qeqaIJb9
https://drive.google.com/open?id=1l8Eey9iF7ht6LMKrn3O915KG74b4aZbf

 

Chrome version: 58-61
OS version: 58-61
Case#: 13902894

Description:
Crashes ID 
Uploaded Crash Report ID e7b702fa9ff6927f 
Uploaded Crash Report ID b8b4accb46dfe4bd 
Uploaded Crash Report ID 3cd898870d4a5eba 
Uploaded Crash Report ID de2b08c4658e3cad 
Uploaded Crash Report ID 3dfc6d00fa0617ee 
Uploaded Crash Report ID 8da97384e29cce2d 
Uploaded Crash Report ID 89d7c6a8f8edeaf7 
Uploaded Crash Report ID 15c836f4d007a603 
Uploaded Crash Report ID fa35f2ec1bda4f2b 
Uploaded Crash Report ID 88c7ca09ae1d2624 
Uploaded Crash Report ID 429cb293a068f254 

- Issue description: 
-Customer called in because the devices were crashing when they were enrolled, after 
the enrollment they would start to crash, they go off and get stuck 
-Devices are in version 58, we wiped one device, did not enrolled it and then we updated it 
-Now the devices in stable but it is working the same way 
-Tested the Crosh Network_diag --hosts and it passed in one device 
-The SN that we have been testing are 
6C27000624 
1S20GE0003USLR08NEBG 
1S20GE0003USLR08NE4G 


Steps to reproduce: 
N/A

Current Behavior / Reproduction: 
-The devices get stuck, or go off for a few seconds and it is unresponsive to any command 

Expected Behavior: 
-Devices should work normally after they have been enrolled 

Drive link to logs: 
https://drive.google.com/open?id=1yw0z_j3BNuY_yHRTXBl9mCU1qeqaIJb9
https://drive.google.com/open?id=1l8Eey9iF7ht6LMKrn3O915KG74b4aZbf