Please deploy autopush 1.9.2 to PRODUCTION

VERIFIED FIXED

Status

VERIFIED FIXED
3 years ago
3 years ago

People

(Reporter: rpapa, Assigned: oremj)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

------------------
RELEASE NOTES
------------------
https://github.com/mozilla-services/autopush/releases

COMPARISONS
https://github.com/mozilla-services/autopush/compare/1.8.1...1.9.0
https://github.com/mozilla-services/autopush/compare/1.9.0...1.9.1
https://github.com/mozilla-services/autopush/compare/1.9.1...1.9.2

TAGS
https://github.com/mozilla-services/autopush/releases/tag/1.9.2
https://github.com/mozilla-services/autopush/commit/5b449dcfc627d6a8a35ca9d83848ba7f5ff7cf16


CHANGELOG
1.9.2 (2016-01-22)
==================

Bug Fixes
---------

* Reduce new UAID's to a single write, this time for real. Issue #300.


1.9.1 (2016-01-22)
==================

Bug Fixes
---------

* Reduce new UAID's to a single write on connect. Issue #300.
* Fixes for GCM JSON encoding rejections and ID assignment. Issue #297.
Assignee: nobody → oremj
Depends on: 1242079
QA Contact: rpappalardo
here's what's currently in production (pre-deployment):

----------------------------
URL CHECKS (PROD)
----------------------------

https://push.services.mozilla.com:

Response time: 0.137781


https://updates.push.services.mozilla.com/health:
{
    "status": "OK", 
    "prod.autopush.storage": {
        "status": "OK"
    }, 
    "version": "1.8.1", 
    "clients": 0, 
    "prod.autopush.router": {
        "status": "OK"
    }
}
Response time: 0.166408


https://updates.push.services.mozilla.com/status:
{
    "status": "OK", 
    "version": "1.8.1"
}
Response time: 0.146495
Status: NEW → ASSIGNED
(Assignee)

Comment 2

3 years ago
1.9.2 has been deployed to production.
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
----------------------------
SUMMARY
----------------------------

:oremj has deployed this release to production and promotion complete

e2e tests passing and stats OK so far, however, there seems to be be a bug where webpush users on reconnect will no longer get notifications (simplepush clients unaffected).

see:
Error on Sentry indicating a bug in webpush 
https://github.com/mozilla-services/autopush/issues/304

No rollback needed, however, we may need to deploy a 1.9.3 tomorrow with a fix.

Verifying 1.9.2 release.


----------------------------
E2E TESTS
----------------------------

DESKTOP PUSH NOTIFICATIONS

using test page:
https://people.mozilla.org/~ewong2/push-notification-test/ - OK

FINDMYDEVICE

Some delay during promotion window, but no errors.
Able to successfully locate, ring and lock STAGE-configured Flame device (w/ B2G 2.2) x 10 - OK

HELLO

Some errors w/ Hello during promotion: "Having technical difficulties" for ~5 mins.
No further problems after that.

Able to place several Hello (Loop) calls successfully between Nightly (46.0a1) and GR (44.0b6) w/ autopush
and verify e2e test calls, room notifications - OK

----------------------------
URL CHECKS (PROD)
----------------------------

https://push.services.mozilla.com:

Response time: 0.911314


https://updates.push.services.mozilla.com/health:
{
    "status": "OK", 
    "prod.autopush.routerv2": {
        "status": "OK"
    }, 
    "prod.autopush.storage": {
        "status": "OK"
    }, 
    "version": "1.9.2", 
    "clients": 0
}
Response time: 0.152052


https://updates.push.services.mozilla.com/status:
{
    "status": "OK", 
    "version": "1.9.2"
}
Response time: 0.153285
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.