|
|
Created:
3 years, 12 months ago by emaxx Modified:
3 years, 11 months ago Reviewers:
Thiemo Nagel CC:
chromium-reviews, oshima+watch_chromium.org, davemoore+watch_chromium.org Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionRe-enable fetching component policies for login screen apps
This CL relands enabling fetching of policies for Chrome OS login screen
apps.
The originally landed code was temporarily disabled due to DMServer
responding with errors when an unknown policy type was requested. Now
this can be enabled back, after the DMServer got fixed to at least
ignore the new policy type (until it starts to actually provide policies
with this type).
BUG=644304, 666720
TEST=re-enabled browser tests;
manual test: sign into an enrolled device, go to chrome://policy
and check that the device policies were fetched successfully
Committed: https://crrev.com/5eb4901df37717dd05fd071a807a0ebaf563f0f3
Cr-Commit-Position: refs/heads/master@{#441015}
Patch Set 1 #Patch Set 2 : Tests cleanup #
Total comments: 2
Patch Set 3 : Rename the for-testing member #
Messages
Total messages: 31 (23 generated)
The CQ bit was checked by emaxx@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
emaxx@chromium.org changed reviewers: + tnagel@chromium.org
Thiemo, PTAL.
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
Description was changed from ========== Re-enable fetching component policies for login screen apps This CL relands enabling fetching of policies for Chrome OS login screen apps. The originally landed code was temporarily disabled due to DMServer responding with errors when an unknown policy type was requested. Now this can be enabled back, after the DMServer got fixed to at least ignore the new policy type (until it starts to actually provide policies with this type). BUG=644304 TEST=browser tests; manual test: sign into an enrolled device, go to chrome://policies and check that the device policies were fetched successfully ========== to ========== Re-enable fetching component policies for login screen apps This CL relands enabling fetching of policies for Chrome OS login screen apps. The originally landed code was temporarily disabled due to DMServer responding with errors when an unknown policy type was requested. Now this can be enabled back, after the DMServer got fixed to at least ignore the new policy type (until it starts to actually provide policies with this type). BUG=644304,666720 TEST=browser tests; manual test: sign into an enrolled device, go to chrome://policies and check that the device policies were fetched successfully ==========
Description was changed from ========== Re-enable fetching component policies for login screen apps This CL relands enabling fetching of policies for Chrome OS login screen apps. The originally landed code was temporarily disabled due to DMServer responding with errors when an unknown policy type was requested. Now this can be enabled back, after the DMServer got fixed to at least ignore the new policy type (until it starts to actually provide policies with this type). BUG=644304,666720 TEST=browser tests; manual test: sign into an enrolled device, go to chrome://policies and check that the device policies were fetched successfully ========== to ========== Re-enable fetching component policies for login screen apps This CL relands enabling fetching of policies for Chrome OS login screen apps. The originally landed code was temporarily disabled due to DMServer responding with errors when an unknown policy type was requested. Now this can be enabled back, after the DMServer got fixed to at least ignore the new policy type (until it starts to actually provide policies with this type). BUG=644304,666720 TEST=re-enabled browser tests; manual test: sign into an enrolled device, go to chrome://policies and check that the device policies were fetched successfully ==========
The CQ bit was checked by emaxx@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
lgtm https://codereview.chromium.org/2603463003/diff/20001/chrome/browser/chromeos... File chrome/browser/chromeos/policy/device_cloud_policy_manager_chromeos.h (right): https://codereview.chromium.org/2603463003/diff/20001/chrome/browser/chromeos... chrome/browser/chromeos/policy/device_cloud_policy_manager_chromeos.h:179: bool is_component_policy_enabled_ = true; Nit: Maybe it would make sense to change polarity and rename to "disable_component_policy_for_testing_"?
The CQ bit was checked by emaxx@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was checked by emaxx@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Description was changed from ========== Re-enable fetching component policies for login screen apps This CL relands enabling fetching of policies for Chrome OS login screen apps. The originally landed code was temporarily disabled due to DMServer responding with errors when an unknown policy type was requested. Now this can be enabled back, after the DMServer got fixed to at least ignore the new policy type (until it starts to actually provide policies with this type). BUG=644304,666720 TEST=re-enabled browser tests; manual test: sign into an enrolled device, go to chrome://policies and check that the device policies were fetched successfully ========== to ========== Re-enable fetching component policies for login screen apps This CL relands enabling fetching of policies for Chrome OS login screen apps. The originally landed code was temporarily disabled due to DMServer responding with errors when an unknown policy type was requested. Now this can be enabled back, after the DMServer got fixed to at least ignore the new policy type (until it starts to actually provide policies with this type). BUG=644304,666720 TEST=re-enabled browser tests; manual test: sign into an enrolled device, go to chrome://policy and check that the device policies were fetched successfully ==========
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
https://codereview.chromium.org/2603463003/diff/20001/chrome/browser/chromeos... File chrome/browser/chromeos/policy/device_cloud_policy_manager_chromeos.h (right): https://codereview.chromium.org/2603463003/diff/20001/chrome/browser/chromeos... chrome/browser/chromeos/policy/device_cloud_policy_manager_chromeos.h:179: bool is_component_policy_enabled_ = true; On 2016/12/29 17:05:21, Thiemo Nagel (slow) wrote: > Nit: Maybe it would make sense to change polarity and rename to > "disable_component_policy_for_testing_"? Done. (Finally named "component_policy_disabled_for_testing".)
The CQ bit was checked by emaxx@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from tnagel@chromium.org Link to the patchset: https://codereview.chromium.org/2603463003/#ps40001 (title: "Rename the for-testing member")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
CQ is committing da patch. Bot data: {"patchset_id": 40001, "attempt_start_ts": 1483068272328620, "parent_rev": "8f1f372431ab1084eecb9d91daf3b5edcb4d4838", "commit_rev": "7321f64bc3fcb31beefb338a8661573153f9669d"}
Message was sent while issue was closed.
Description was changed from ========== Re-enable fetching component policies for login screen apps This CL relands enabling fetching of policies for Chrome OS login screen apps. The originally landed code was temporarily disabled due to DMServer responding with errors when an unknown policy type was requested. Now this can be enabled back, after the DMServer got fixed to at least ignore the new policy type (until it starts to actually provide policies with this type). BUG=644304,666720 TEST=re-enabled browser tests; manual test: sign into an enrolled device, go to chrome://policy and check that the device policies were fetched successfully ========== to ========== Re-enable fetching component policies for login screen apps This CL relands enabling fetching of policies for Chrome OS login screen apps. The originally landed code was temporarily disabled due to DMServer responding with errors when an unknown policy type was requested. Now this can be enabled back, after the DMServer got fixed to at least ignore the new policy type (until it starts to actually provide policies with this type). BUG=644304,666720 TEST=re-enabled browser tests; manual test: sign into an enrolled device, go to chrome://policy and check that the device policies were fetched successfully Review-Url: https://codereview.chromium.org/2603463003 ==========
Message was sent while issue was closed.
Committed patchset #3 (id:40001)
Message was sent while issue was closed.
Description was changed from ========== Re-enable fetching component policies for login screen apps This CL relands enabling fetching of policies for Chrome OS login screen apps. The originally landed code was temporarily disabled due to DMServer responding with errors when an unknown policy type was requested. Now this can be enabled back, after the DMServer got fixed to at least ignore the new policy type (until it starts to actually provide policies with this type). BUG=644304,666720 TEST=re-enabled browser tests; manual test: sign into an enrolled device, go to chrome://policy and check that the device policies were fetched successfully Review-Url: https://codereview.chromium.org/2603463003 ========== to ========== Re-enable fetching component policies for login screen apps This CL relands enabling fetching of policies for Chrome OS login screen apps. The originally landed code was temporarily disabled due to DMServer responding with errors when an unknown policy type was requested. Now this can be enabled back, after the DMServer got fixed to at least ignore the new policy type (until it starts to actually provide policies with this type). BUG=644304,666720 TEST=re-enabled browser tests; manual test: sign into an enrolled device, go to chrome://policy and check that the device policies were fetched successfully Committed: https://crrev.com/5eb4901df37717dd05fd071a807a0ebaf563f0f3 Cr-Commit-Position: refs/heads/master@{#441015} ==========
Message was sent while issue was closed.
Patchset 3 (id:??) landed as https://crrev.com/5eb4901df37717dd05fd071a807a0ebaf563f0f3 Cr-Commit-Position: refs/heads/master@{#441015}
Message was sent while issue was closed.
A revert of this CL (patchset #3 id:40001) has been created in https://codereview.chromium.org/2621413007/ by tnagel@chromium.org. The reason for reverting is: I'm very sorry I have to revert this since it's breaking device policy updates. https://bugs.chromium.org/p/chromium/issues/detail?id=679956#c7. |