Issue 146459 in chromium: Device pointing to (DM/Gaia) Staging environment fails Enterprise Enrollment

[chro...@googlecode.com]

Status: Untriaged
Owner: ----
CC: scunning...@chromium.org, kr...@chromium.org, debs...@chromium.org
Labels: Type-Regression Pri-0 Area-Internals OS-Chrome Feature-Enterprise

New issue 146459 by krishna...@chromium.org: Device pointing to (DM/Gaia)
Staging environment fails Enterprise Enrollment
http://code.google.com/p/chromium/issues/detail?id=146459

Version: R23,R22;2486.0.0;Alex

Staging DMServer & Gaia URL's:(that the device is pointing to)
grep 'DMS\|gaia' /sbin/session_manager_setup.sh (attached)

DMSERVER="https://cros-auto.sandbox.google.com/devicemanagement/data/api"
--gaia-url-path=/accounts \
--gaia-host=gaiastaging.corp.google.com \
--gaia-oauth-host=gaiastaging.corp.google.com \
--device-management-url="$DMSERVER" \

What steps will reproduce the problem?
1.Point the device to a staging environment(ie, DM server/gaia staging)
--(Procedure to point to staging can be found at link below)
2.Step through OOBE and press Ctrl-E on the sign in screen to navigate to
Enterprise Enrollment signin screen
3.Attempt to login using valid Enterprise login credentials for a staging
domain

Steps to point the device to a staging environment can be found in
the 'CrOS Enterprise Testing Tips and HowTos' document at:
https://docs.google.com/a/google.com/document/d/1V5sGYG5fuyyBPU6l4IYKF82JaEeXhaI1Snlikc6NNyY/edit?pli=1#heading=h.l4ygsy8mvi9t


What is the expected output? What do you see instead?
Expected Output:The device should enroll into the staging domain
Actual Output: The device does not enroll into the staging domain but
displays a network connection error instead(misleading error maybe?? as I'm
able to ping google.com)


Attached: Screenshot of Screen Displayed on Enrollment failure, device
logs, session_manager_setup.sh from the device(Modifications are made to
this file to point the device to staging)



Please use labels and text to provide additional information.

Attachments:
Screenshot 2012-09-05 at 12.43.32 AM.png 731 KB
log-090512-004450.tar.bz2 548 KB
session_manager_setup.sh 13.3 KB

[chro...@googlecode.com]

Updates:
Cc: binz...@chromium.org t...@chromium.org

Comment #1 on issue 146459 by joaod...@chromium.org: Device pointing to

(DM/Gaia) Staging environment fails Enterprise Enrollment
http://code.google.com/p/chromium/issues/detail?id=146459

The logs show that fetching the DM token failed with
DM_STATUS_TEMPORARY_UNAVAILABLE. This means that the gaia steps are OK, and
the first DMServer step failed.

Unfortunately DM_STATUS_TEMPORARY_UNAVAILABLE can mean 3 things:

- 404 from server (invalid URL?)
- 500 from server (a real temporary error, retrying should eventually work?)
- 503 from server (same?)

So it's either a temporary problem with the server, or the URL is invalid.

@Bin, @Raymond: the dmserver URL looks good to me, can you confirm? Is that
server up and running without problems?

[chro...@googlecode.com]

Comment #2 on issue 146459 by joaod...@chromium.org: Device pointing to

(DM/Gaia) Staging environment fails Enterprise Enrollment
http://code.google.com/p/chromium/issues/detail?id=146459

DM_STATUS_TEMPORARY_UNAVAILABLE can actually be any error between 500 and
599. I'll try to repro locally.

[chro...@googlecode.com]

Comment #3 on issue 146459 by bugdro...@chromium.org: Device pointing to

(DM/Gaia) Staging environment fails Enterprise Enrollment

http://code.google.com/p/chromium/issues/detail?id=146459#c3

The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=154918

------------------------------------------------------------------------
r154918 | joaod...@chromium.org | 2012-09-05T09:08:33.625343Z

Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/policy/device_management_service.cc?r1=154918&r2=154917&pathrev=154918

Always log the exact error code from the dmserver.

BUG=146459

Review URL: https://chromiumcodereview.appspot.com/10920088
------------------------------------------------------------------------

[chro...@googlecode.com]

Comment #4 on issue 146459 by t...@google.com: Device pointing to (DM/Gaia)

Staging environment fails Enterprise Enrollment
http://code.google.com/p/chromium/issues/detail?id=146459

Caused by incorrect healthz string when I moved over the chrome os test
server last week. I sent out CL 33583292 to fix this. I will push this
tomorrow.

cros-auto.sandbox should now work as I put in a workaround.

[chro...@googlecode.com]

Updates:
Owner: krishna...@chromium.org

Comment #5 on issue 146459 by joaod...@chromium.org: Device pointing to

(DM/Gaia) Staging environment fails Enterprise Enrollment
http://code.google.com/p/chromium/issues/detail?id=146459

@krishnargv: can you test again now that Raymond's fix is in?

[chro...@googlecode.com]

Comment #7 on issue 146459 by t...@google.com: Device pointing to (DM/Gaia)

Staging environment fails Enterprise Enrollment
http://code.google.com/p/chromium/issues/detail?id=146459

Hi,

The fix is not in yet. I need to wait for the push by the mobile team.

In the meantime, you can test with cros-auto.

[chro...@googlecode.com]

Updates:
Status: Verified

Comment #10 on issue 146459 by joaod...@chromium.org: Device pointing to

(DM/Gaia) Staging environment fails Enterprise Enrollment
http://code.google.com/p/chromium/issues/detail?id=146459

(No comment was entered for this change.)