Revert of Fix handling of device cloud signing policy key rotation

Revert of Fix handling of device cloud signing policy key rotation (patchset #8 id:140001 of https://codereview.chromium.org/2558543003/ )

Reason for revert:
Broke KeyRotationDeviceCloudPolicyTest.Basic test
https://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%20Tests%20%281%29/builds/34579

Original issue's description:
> Fix handling of device cloud signing policy key rotation
> 
> This CL fixes issues with handling of the signing key rotation for the
> device policy. There were some issues with not loading the updated
> owner key right after the new policy is stored. Even though the key
> would eventually be loaded thanks to the OwnerKeySet signal emitted
> by the session manager, there may be some window during which the old
> key is still used on the Chrome side.
> 
> Also the CL adds a browser end-to-end test for browser policy key
> rotation (using a local policy test server). Some fake testing-only
> stubs were also fixed in order to support changing the signing keys
> (similar to how this is handled by the session manager).
> 
> BUG=671659, 668716
> TEST=new browser test
> 
> Review-Url: https://codereview.chromium.org/2558543003
> Cr-Commit-Position: refs/heads/master@{#454506}
> Committed: https://chromium.googlesource.com/chromium/src/+/6581fa97d9ac35a9c541856a0acc04c8be2cfc20

TBR=atwilson@chromium.org,mnissler@chromium.org,stevenjb@chromium.org,emaxx@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=671659, 668716
Review-Url: https://codereview.chromium.org/2727863004
Cr-Commit-Position: refs/heads/master@{#454541}
Committed: https://chromium.googlesource.com/chromium/src/+/3fa1b666a54ad027289ec0c1752fcfb6d138b512

[alph, 2017-03-03 07:58:32]

The CQ bit was checked by alph@chromium.org

[alph, 2017-03-03 07:58:33]

Created Revert of Fix handling of device cloud signing policy key rotation

[commit-bot: I haz the power, 2017-03-03 07:58:46]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-03-03 07:59:25]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1488527912916790, "parent_rev":
"6b24a72f48297bc66d3e5c67f718f7d6797b4a5c", "commit_rev":
"3fa1b666a54ad027289ec0c1752fcfb6d138b512"}

[commit-bot: I haz the power, 2017-03-03 08:00:03]

Description was changed from

==========
Revert of Fix handling of device cloud signing policy key rotation (patchset #8
id:140001 of https://codereview.chromium.org/2558543003/ )

Reason for revert:
Broke KeyRotationDeviceCloudPolicyTest.Basic test
https://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%...

Original issue's description:
> Fix handling of device cloud signing policy key rotation
> 
> This CL fixes issues with handling of the signing key rotation for the
> device policy. There were some issues with not loading the updated
> owner key right after the new policy is stored. Even though the key
> would eventually be loaded thanks to the OwnerKeySet signal emitted
> by the session manager, there may be some window during which the old
> key is still used on the Chrome side.
> 
> Also the CL adds a browser end-to-end test for browser policy key
> rotation (using a local policy test server). Some fake testing-only
> stubs were also fixed in order to support changing the signing keys
> (similar to how this is handled by the session manager).
> 
> BUG=671659,668716
> TEST=new browser test
> 
> Review-Url: https://codereview.chromium.org/2558543003
> Cr-Commit-Position: refs/heads/master@{#454506}
> Committed:
https://chromium.googlesource.com/chromium/src/+/6581fa97d9ac35a9c541856a0acc...

TBR=atwilson@chromium.org,mnissler@chromium.org,stevenjb@chromium.org,emaxx@c...
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=671659,668716
==========

to

==========
Revert of Fix handling of device cloud signing policy key rotation (patchset #8
id:140001 of https://codereview.chromium.org/2558543003/ )

Reason for revert:
Broke KeyRotationDeviceCloudPolicyTest.Basic test
https://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%...

Original issue's description:
> Fix handling of device cloud signing policy key rotation
> 
> This CL fixes issues with handling of the signing key rotation for the
> device policy. There were some issues with not loading the updated
> owner key right after the new policy is stored. Even though the key
> would eventually be loaded thanks to the OwnerKeySet signal emitted
> by the session manager, there may be some window during which the old
> key is still used on the Chrome side.
> 
> Also the CL adds a browser end-to-end test for browser policy key
> rotation (using a local policy test server). Some fake testing-only
> stubs were also fixed in order to support changing the signing keys
> (similar to how this is handled by the session manager).
> 
> BUG=671659,668716
> TEST=new browser test
> 
> Review-Url: https://codereview.chromium.org/2558543003
> Cr-Commit-Position: refs/heads/master@{#454506}
> Committed:
https://chromium.googlesource.com/chromium/src/+/6581fa97d9ac35a9c541856a0acc...

TBR=atwilson@chromium.org,mnissler@chromium.org,stevenjb@chromium.org,emaxx@c...
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=671659,668716

Review-Url: https://codereview.chromium.org/2727863004
Cr-Commit-Position: refs/heads/master@{#454541}
Committed:
https://chromium.googlesource.com/chromium/src/+/3fa1b666a54ad027289ec0c1752f...
==========

[commit-bot: I haz the power, 2017-03-03 08:00:04]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/3fa1b666a54ad027289ec0c1752f...

[emaxx, 2017-03-03 18:32:48]

alph@/others: Any ideas on why could the test fail on builders, but succeed when
running trybots from CL?
Are there any significant changes in the environment, or maybe with regard to
the the tests isolation?