Bug 1601680 Comment 9 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
Deployed to prod. For QA:

normandy:

*   :bpitts can you run `./manage.py update_signatures --force` on the prod admin?
Revision 1 by
on 
Deployed to prod. For QA:

monitors:

    proxy monitor: 
    monitor: 

AMO:

*  TODO submit the test addon

Kinto/Remote Settings:

*  blocked on normandy signing

normandy:

*   :bpitts can you run `./manage.py update_signatures --force` on the prod admin?
Revision 2 by
on 
Deployed to prod. For QA:

monitors:

* proxy monitor: 
* monitor: 

AMO:

*  TODO submit the test addon

Kinto/Remote Settings:

*  blocked on normandy signing

normandy:

*   :bpitts can you run `./manage.py update_signatures --force` on the prod admin?
Revision 3 by
on 
Deployed to prod. For QA:

monitors:

* proxy monitor: 
* monitor: 

AMO:

*  submitted the test addon; pending review

Kinto/Remote Settings:

*  blocked on normandy signing

normandy:

*   :bpitts can you run `./manage.py update_signatures --force` on the prod admin?
Revision 4 by
on 
Deployed to prod. For QA:

monitors:

* proxy monitor: 
* monitor: 

AMO:

*  submitted the test addon; pending review

Kinto/Remote Settings:

*  blocked on normandy signing (delivery checks are green)

normandy:

*   :bpitts can you run `./manage.py update_signatures --force` on the prod admin?
Revision 5 by
on 
Deployed to prod. For QA:

monitors:

* proxy monitor: 
* monitor: 

AMO:

*  submitted the test addon; pending review

Kinto/Remote Settings:

*  blocked on normandy signing (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?
Revision 6 by
on 
Deployed to prod. For QA:

monitors:

* proxy monitor: 
* monitor: 

AMO:

*  submitted the test addon; pending review

Kinto/Remote Settings:

*  ~blocked on normandy signing~ (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?
Revision 7 by
on 
Deployed to prod. For QA:

monitors:

* proxy monitor: 
* monitor: 

AMO:

*  submitted the test addon; pending review

Kinto/Remote Settings:

*  ~blocked on normandy signing~ kinto 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?
Revision 8 by
on 
Deployed to prod. For QA:

monitors:

* proxy monitor: 
* monitor: 

AMO:

*  submitted the test addon; ~pending review~. Signature looks good.

Kinto/Remote Settings:

*  ~blocked on normandy signing~ kinto 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?
Revision 9 by
on 
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 signing~ kinto 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?

Back to Bug 1601680 Comment 9