New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 602993 link

Starred by 8 users

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: May 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

DeviceManagementService should have more robust retry logic

Project Member Reported by atwilson@chromium.org, Apr 13 2016

Issue description

We are seeing issues in the field for auto-starting kiosk sessions where the kiosk session starts before the internet connection is established, so device management activities (like policy fetch and status upload) that happen on startup fail.

We should extend the retry logic in DeviceManagementService so that certain network errors (like INTERNET_DISCONNECTED) retry after a delay.
 
Cc: sduraisamy@chromium.org

Comment 2 by kotah@chromium.org, Apr 22 2016

Cc: kotah@chromium.org
Components: Enterprise
Labels: Hotlist-Enterprise OS-Chrome
Status: Assigned (was: Untriaged)
Hi Márton, thank you for taking this bug. Any update?
Status: Started (was: Assigned)
It's in progress, the CL is at https://codereview.chromium.org/1928013004, but I think there are still some cases where we don't retry (and also some browser tests are failing - they time out because of the retry delays).
Status: Fixed (was: Started)
Cc: trapti@chromium.org

Comment 9 by trapti@chromium.org, May 24 2016

Status: Verified (was: Fixed)
Working with Managed Chrome App in Peppy Device.Tried various connect disconnect of the Network and uploaded new policy files to check.

M	ChromeOS	Chrome	ARC	Type	Channel
52	8352.0.0	52.0.2739.0	2890844	release	dev


Sign in to add a comment