Reland: No longer start up profile if there was an error fetching policy.

Reland: No longer start up profile if there was an error fetching policy.

Changed UserCloudPolicyManagerChromeOS to no longer complete profile
initialization if there is an error fetching policy. Instead, we shutdown the
user and force a policy load the next time we try to startup that user.

BUG=532317
TBR=vitalybuka@chromium.org

Committed: https://crrev.com/01a589c605a9ead2754a51a5ef2c916361c6be0d
Cr-Commit-Position: refs/heads/master@{#377288}

[Andrew T Wilson (Slow), 2016-02-24 13:31:19]

atwilson@chromium.org changed reviewers:
+ tnagel@google.com

[Andrew T Wilson (Slow), 2016-02-24 13:31:19]

Relanding this since it was reverted because some cros VMTests needed to pass a
new flag after this CL.

[Andrew T Wilson (Slow), 2016-02-24 13:31:25]

The CQ bit was checked by atwilson@chromium.org

[commit-bot: I haz the power, 2016-02-24 13:33:48]

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

[commit-bot: I haz the power, 2016-02-24 14:31:06]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-02-24 14:32:34]

Description was changed from

==========
Reland: No longer start up profile if there was an error fetching policy.

Changed UserCloudPolicyManagerChromeOS to no longer complete profile
initialization if there is an error fetching policy. Instead, we shutdown the
user and force a policy load the next time we try to startup that user.

BUG=532317
TBR=vitalybuka@chromium.org
==========

to

==========
Reland: No longer start up profile if there was an error fetching policy.

Changed UserCloudPolicyManagerChromeOS to no longer complete profile
initialization if there is an error fetching policy. Instead, we shutdown the
user and force a policy load the next time we try to startup that user.

BUG=532317
TBR=vitalybuka@chromium.org

Committed: https://crrev.com/01a589c605a9ead2754a51a5ef2c916361c6be0d
Cr-Commit-Position: refs/heads/master@{#377288}
==========

[commit-bot: I haz the power, 2016-02-24 14:32:35]

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

[stevenjb, 2016-02-24 20:27:03]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/1737453003/ by stevenjb@chromium.org.

The reason for reverting is: Still causing failures here:
https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/Lumpy%20%28ch...

It's possible that the telemetry fixes have not propagated to the builder yet.
.