Closed Bug 1390918 Opened 7 years ago Closed 7 years ago

[Shield][OptOut Studies] Recipe execution fails (normandy-admin.stage)

Categories

(Shield :: General, defect)

defect
Not set
blocker

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: aflorinescu, Assigned: osmose)

References

Details

[Enviroment:]
-Ubuntu 16.04 x64
-57.0a1	20170816100153

[Pre-requisites:]
You need access to Admin interface (https://normandy-admin.stage.mozaws.net/control/)
1. Obtain a copy of Firefox with the SHIELD recipe client system add-on installed. You can check about:support to ensure that you have it.
2. Set the extensions.shield-recipe-client.dev_mode preference to true to run recipes immediately on startup.
3. Set the extensions.shield-recipe-client.logging.level preference to 0 to enable more logging.
4. Set the security.content.signature.root_hash preference to DB:74:CE:58:E4:F9:D0:9E:E0:42:36:BE:6C:C5:C4:F6:6A:E7:74:7D:C0:21:42:7A:03:BC:2F:57:0C:8B:9B:90
5. Set the preference value for extensions.shield-recipe-client.api_url set to https://normandy.stage.mozaws.net/api/v1



[Steps:]
1. Create the simplest Opt-Out Recipe. - filter 1==1, all FF users in the bucket.
2. Set the preconditions and restart FF.
3. Check browser console and about:addons


[Expected Result:]
Recipe is executed.


[Actual Result:]
1502896437509	extensions.shield-recipe-client.recipe-runner	ERROR	Could not execute recipe test opt.
See https://pastebin.mozilla.org/9029858 for the full browser console.
Assignee: nobody → mkelly
Commits pushed to master at https://github.com/mozilla/normandy

https://github.com/mozilla/normandy/commit/c1a72fe95f9f2039f319c45cd8bdb0d30835e658
Fix bug 1390918: Move DLL plugin to control-only webpack config.

Action code is served as a single chunk of JS and does not function
properly with the split bundles that the DLL plugin produces.

https://github.com/mozilla/normandy/commit/8c38091bfe9df90f2a50bc54253c2fe1dfef9779
Merge pull request #990 from Osmose/action-dll

Fix bug 1390918: Move DLL plugin to control-only webpack config.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
v70 has been deployed to prod, containing this fix.
You need to log in before you can comment on or make changes to this bug.