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

Revert of Reland: No longer start up profile if there was an error fetching policy. (patchset #1 id:1 of https://codereview.chromium.org/1727413002/ )

Reason for revert:
Still causing failures here:
https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/Lumpy%20%28chrome%29/builds/18722

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

Original issue's description:
> 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}

TBR=vitalybuka@chromium.org,tnagel@google.com,atwilson@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=532317
Committed: https://crrev.com/6c9db5f91e463b362258634356f4d3bca897f0ef
Cr-Commit-Position: refs/heads/master@{#377371}

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

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

[commit-bot: I haz the power, 2016-02-24 20:35:41]

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

[commit-bot: I haz the power, 2016-02-24 20:42:26]

Description was changed from

==========
Revert of Reland: No longer start up profile if there was an error fetching
policy. (patchset #1 id:1 of https://codereview.chromium.org/1727413002/ )

Reason for revert:
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.


Original issue's description:
> 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}

TBR=vitalybuka@chromium.org,tnagel@google.com,atwilson@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=532317
==========

to

==========
Revert of Reland: No longer start up profile if there was an error fetching
policy. (patchset #1 id:1 of https://codereview.chromium.org/1727413002/ )

Reason for revert:
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.


Original issue's description:
> 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}

TBR=vitalybuka@chromium.org,tnagel@google.com,atwilson@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=532317
==========

[commit-bot: I haz the power, 2016-02-24 20:42:27]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-02-24 20:44:35]

Description was changed from

==========
Revert of Reland: No longer start up profile if there was an error fetching
policy. (patchset #1 id:1 of https://codereview.chromium.org/1727413002/ )

Reason for revert:
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.


Original issue's description:
> 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}

TBR=vitalybuka@chromium.org,tnagel@google.com,atwilson@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=532317
==========

to

==========
Revert of Reland: No longer start up profile if there was an error fetching
policy. (patchset #1 id:1 of https://codereview.chromium.org/1727413002/ )

Reason for revert:
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.

Original issue's description:
> 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}

TBR=vitalybuka@chromium.org,tnagel@google.com,atwilson@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=532317

Committed: https://crrev.com/6c9db5f91e463b362258634356f4d3bca897f0ef
Cr-Commit-Position: refs/heads/master@{#377371}
==========

[commit-bot: I haz the power, 2016-02-24 20:44:36]

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