New issue
Advanced search Search tips

Issue 751436 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Active Directory enrollment breaks autotests

Project Member Reported by ljusten@chromium.org, Aug 2 2017

Issue description

An Active Directory enrolled device cannot be used for autotests. It looks like the 

Steps To Reproduce:
(1) Enroll the device into an Active Directory domain. Don't add any user, just Gaia login and domain join screen.
(2) Run some autotest, e.g.
      test_that -b $BOARD $DEVICE_IP login_LoginSuccess

Expected Result:
Test succeeds.

Actual Result:
Test gets stuck 100%.

It looks like Chrome restarts immediately and forces the "Sign in to ad.domain.com" screen. The screen requested by the autotest (e.g. Gaia login) is never shown. It's probably related to the presence of install_attributes.pb that lock the device to Active Directory enrollment.


 
Labels: Pri-3
Labels: -Pri-3 Pri-2
Labels: -Pri-2 Pri-3
Sorry for the noise
Status: WontFix (was: Assigned)
AuthPolicy tests clean up TPM (and enrollment state) now, so this should be a non-issue.

Sign in to add a comment