Deploy Autograph 3.11.4 train-8
Categories
(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)
Tracking
(Not tracked)
People
(Reporter: u581815, Assigned: u581815)
References
(Blocks 1 open bug)
Details
Please deploy Autograph {{TAG}} to staging and perform QA testing.
https://mana.mozilla.org/wiki/display/SVCOPS/Autograph#Autograph-QA
last train: https://bugzilla.mozilla.org/show_bug.cgi?id=1594155
- tag: https://github.com/mozilla-services/autograph/releases/tag/3.11.4
- image: https://hub.docker.com/r/mozilla/autograph/tags/?page=1&name=3.11.4
- diff from train-7: https://github.com/mozilla-services/autograph/compare/3.10.1...3.11.4
infra changes: switch alerting from datadog to influxdb
config changes: bug 1613113, bug 1613108, bug 1614370, https://github.com/mozilla-services/autograph/issues/414
:hwine and :ulfr r? on the train-8 config changes (currently at commit b2065c7a8008713bc9e1d77124d709aa544b5b6e)
Comment 3•5 years ago
|
||
Except for the apk1->2 changes that are still being discussed with :jlorenzo, r+
on autograph-hiera-sops changes from 13af68632aa32d4c3f798a8571a810fda4ab1e7d to b2065c7a8008713bc9e1d77124d709aa544b5b6e.
Comment 4•5 years ago
|
||
Except for the apk1->2 changes that are still being discussed with :jlorenzo
Signed off on those changes as well. Train can go out.
Deployed to stage.
QA:
monitors passing:
- proxy monitor: autograph-stage-default-monitor-LambdaFunction passing rid ffdc67fd-3da0-4b4c-b8ee-02b65cba80c1
- monitor: autograph-autographstage-default-mo-LambdaFunction passing rid 88bdd5c7-3e09-429f-80a1-75b60c2b0713
AMO:
- submitted the test addon w/o errors; signed and validated without errors
Kinto/Remote Settings:
blocked on normandy signingkinto-lambda-refresh_signature passed rid 6b730809-87ff-4dc3-be04-b95fe6a26cc9 and downstream delivery checks are green
RelEng:
- :aki can you test MAR signing? https://moz-releng-docs.readthedocs.io/en/latest/procedures/Testing_Autograph.html#testing-autograph-stage
normandy:
- :bpitts can you run
./manage.py update_signatures --force
on the stage admin?
Comment 7•5 years ago
|
||
Looks like our testing config broke over the past couple months. Landed a fix: https://phabricator.services.mozilla.com/D64204
That'll merge, and we'll get some nightlies, and then I can test. That may be tomorrow.
Deployed to prod. For QA:
monitors:
- proxy monitor: passing rid 85bfad17-6de5-4dd6-80d0-39961142c1f4
- monitor: passing rid 4dec808c-4d1b-4c45-84f7-5c1e83400996
(:bobm opened https://github.com/mozilla-services/cloudops-deployment/pull/3702 to account for drift in changes we made to get it passing)
AMO:
- submitted the test addon;
pending review. Signature looks good.
Kinto/Remote Settings:
blocked on normandy signingkinto refresh lambda succeeded rid 1b86f5c2-a2cf-4aac-a6c6-8f60c120f69b and delivery checks are green
RelEng:
- :aki confirmed that MAR signing is OK
normandy:
- :bpitts can you run
./manage.py update_signatures --force
on the prod admin?
Assignee | ||
Comment 11•5 years ago
|
||
OK thanks bpitts and aki.
The app server looks good.
:bobm is deploying edge @ 1.0.10 to stage
Assignee | ||
Comment 12•5 years ago
|
||
edge stage and prod deployed and QA for them is green.
Description
•