GitLab

We have many extensions stuck in CREATED stage which is reported
in ExtensionManagement::UpdateForcedExtensions when extension list is
fetched from kInstallForceList pref. We add the extensions to
|settings_by_id_| dictionary. This dictionary may be overridden by
the entries in kExtensionManagement pref and it is possible that
the extensions which are listed in forced list may be listed
in kExtensionManagement pref as "allowed" or "blocked". In these
cases, we might not install the extension as ExtensionSettings policy
overrides the policy for force installed extensions.

This CL adds a new failure reason which is reported when extension
listed in forced list policy has its installation mode
overridden by ExtensionSettings policy to something else.

Bug: 989526
Change-Id: I20995df211d5e09492c35c09e7c5152deba2fdd5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2390181
Commit-Queue: Swapnil Gupta <swapnilgupta@google.com>
Reviewed-by: Oleg Davydov <burunduk@chromium.org>
Reviewed-by: Saurabh Nijhara <snijhara@google.com>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: Brian White <bcwhite@chromium.org>
Reviewed-by: Sergey Poromov <poromov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805702}