Closed
Bug 1392982
Opened 7 years ago
Closed 7 years ago
[Shield][Admin] Cannot create any new Recipes
Categories
(Shield :: General, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: miriapodzemos.my, Unassigned)
References
Details
Attachments
(1 file)
109.58 KB,
image/png
|
Details |
Preconditions You need access to Admin interface (for this Test Suite, 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 [Environment:] 57.0a1 20170822142709 MAC OsX 10.12 [Steps:] 1. Open FF with a new profile. 2. Open admin at https://normandy-admin.stage.mozaws.net/control/recipe/ 3. Fill all the required fields (see screenshot) 4. Save new recipe [Actual Result:] The recipe is not saved: "! Recipe cannot be saved. Please correct any errors listed in the form below." error returned Check https://pastebin.mozilla.org/9030345 [Expected Result:] The recipe should be saved [Note:]Ubuntu 16.04 Not reproducible
Comment 1•7 years ago
|
||
update: Not reproducible on Windows 10 Pro x64 either.
Comment 2•7 years ago
|
||
Your account didn't have permission to create recipes, and we haven't fixed the error message yet to be more specific about it. Sorry! I've given your account on staging the same permissions as Adrian's, so you should be good now. Feel free to reopen if that's not the case!
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Thank you. I can create recipes now. Verified Fixed
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•