cros: Fix unexpected cryptohome failure UI

cros: Fix unexpected cryptohome failure UI

TokenHandleFetcher::FillForNewUser should be called when there is no
existing TokenHandle. Existing users should all go through the
BackfillToken path. This would let the login screen code test against
existing TokenHandle rather than racing with FillForNewUser code.

BUG=596502
Committed: https://crrev.com/9231ba274a1c6525bf06cfc1a214fae2967663b7
Cr-Commit-Position: refs/heads/master@{#382342}

[xiyuan, 2016-03-21 18:11:19]

Description was changed from

==========
cros: Fix unexpected cryptohoem failure UI

TokenHandleFetcher::FillForNewUser should be called when there is no
existing TokenHandle. Existing users should all go through the
BackfillToken path. This would let the login screen code test against
existing TokenHandle rather than racing with FillForNewUser code.

BUG=596502
==========

to

==========
cros: Fix unexpected cryptohome failure UI

TokenHandleFetcher::FillForNewUser should be called when there is no
existing TokenHandle. Existing users should all go through the
BackfillToken path. This would let the login screen code test against
existing TokenHandle rather than racing with FillForNewUser code.

BUG=596502
==========

[xiyuan, 2016-03-21 18:11:58]

xiyuan@chromium.org changed reviewers:
+ dzhioev@chromium.org

[achuithb, 2016-03-21 18:14:40]

achuith@chromium.org changed reviewers:
+ achuith@chromium.org

[achuithb, 2016-03-21 18:14:41]

lgtm

[xiyuan, 2016-03-21 18:17:22]

Thanks for the quick review.

[xiyuan, 2016-03-21 18:17:27]

The CQ bit was checked by xiyuan@chromium.org

[commit-bot: I haz the power, 2016-03-21 18:17:59]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1824693002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1824693002/1

[commit-bot: I haz the power, 2016-03-21 18:50:37]

Description was changed from

==========
cros: Fix unexpected cryptohome failure UI

TokenHandleFetcher::FillForNewUser should be called when there is no
existing TokenHandle. Existing users should all go through the
BackfillToken path. This would let the login screen code test against
existing TokenHandle rather than racing with FillForNewUser code.

BUG=596502
==========

to

==========
cros: Fix unexpected cryptohome failure UI

TokenHandleFetcher::FillForNewUser should be called when there is no
existing TokenHandle. Existing users should all go through the
BackfillToken path. This would let the login screen code test against
existing TokenHandle rather than racing with FillForNewUser code.

BUG=596502
==========

[commit-bot: I haz the power, 2016-03-21 18:50:38]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-03-21 18:51:37]

Description was changed from

==========
cros: Fix unexpected cryptohome failure UI

TokenHandleFetcher::FillForNewUser should be called when there is no
existing TokenHandle. Existing users should all go through the
BackfillToken path. This would let the login screen code test against
existing TokenHandle rather than racing with FillForNewUser code.

BUG=596502
==========

to

==========
cros: Fix unexpected cryptohome failure UI

TokenHandleFetcher::FillForNewUser should be called when there is no
existing TokenHandle. Existing users should all go through the
BackfillToken path. This would let the login screen code test against
existing TokenHandle rather than racing with FillForNewUser code.

BUG=596502

Committed: https://crrev.com/9231ba274a1c6525bf06cfc1a214fae2967663b7
Cr-Commit-Position: refs/heads/master@{#382342}
==========

[commit-bot: I haz the power, 2016-03-21 18:51:38]

Patchset 1 (id:??) landed as
https://crrev.com/9231ba274a1c6525bf06cfc1a214fae2967663b7
Cr-Commit-Position: refs/heads/master@{#382342}