New issue
Advanced search Search tips

Issue 689780 link

Starred by 3 users

Issue metadata

Status: Verified
Owner:
Closed: Feb 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Intiail AD join fails but is successful on second attempt.

Project Member Reported by krishna...@chromium.org, Feb 8 2017

Issue description

Chrome Version: 58.0.3001.0 -- Dev
Chrome OS Version: 9260.0.0
Chrome OS Platform: Peppy
Network info: WiFi

Summary: AD join fails on the first attempt. 
The 'Oops something went wrong when trying to join the domain' error is displayed on the initial AD join attempt.(Screenshot attached) 
But 'AD Join successful message' is displayed in the messages logs and  the computer name is added to the AD dashboard. 

On clicking the Try Again button, the 'Join Device to domain' screen is displayed with the Computer name and Username pre-filled, 
On adding password and clicking Next --> the Enterprise Enrollment successful screen is displayed. 

Steps To Reproduce(same as above):
(1) Ctrl _Alt+ Shift+ A. Provide the credentials
(2) On the Join Device to domain screen, enter a computer Name and Username/password and click Next.--> the Oops Error is displayed.
3) Click Try Again--> the Join Device to domain screen is displayed with the Computer name and Username pre-filled.
4) Enter the password and Click Next --> the Enterprise Enrollment successful screen is displayed.

This does not occur on (R57 dev:9202.18.0:57.0.2987.32)
 
Cc: tnagel@chromium.org ljusten@chromium.org rsorokin@chromium.org
Labels: -Type-Bug -Pri-3 Pri-2 Type-Bug-Regression
Status: Available (was: Unconfirmed)
Screenshot 2017-02-07 at 5.00.00 PM.png
582 KB View Download
log-020717-172125.tar.gz
228 KB Download
Description: Show this description
 Issue 688376  has been merged into this issue.
Cc: -rsorokin@chromium.org
Owner: rsorokin@chromium.org
Status: Started (was: Available)
Project Member

Comment 5 by bugdroid1@chromium.org, Feb 8 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/fa52cd2282200f607c2eabbc438e18d941dbd7b0

commit fa52cd2282200f607c2eabbc438e18d941dbd7b0
Author: rsorokin <rsorokin@chromium.org>
Date: Wed Feb 08 11:03:03 2017

Chromad: Extend D-BUS timeout for the domain join call

BUG= 689780 
TBR=tnagel@chromium.org

Review-Url: https://codereview.chromium.org/2681673003
Cr-Commit-Position: refs/heads/master@{#448952}

[modify] https://crrev.com/fa52cd2282200f607c2eabbc438e18d941dbd7b0/chromeos/dbus/auth_policy_client.cc

Status: Fixed (was: Started)

Comment 7 by trapti@chromium.org, Feb 15 2017

Status: Verified (was: Fixed)
Could connect @first attempt in M58 Peppy

M	ChromeOS	Chrome	ARC	Type	Channel
58	9284.0.0	58.0.3011.0	(multiple)	release	dev

Sign in to add a comment