Please deploy autopush 1.19.3 to PRODUCTION

VERIFIED FIXED

Status

Cloud Services
Operations: Autopush
VERIFIED FIXED
a year ago
a year ago

People

(Reporter: Cloud Services QA, Assigned: oremj)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

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

COMPARISONS
https://github.com/mozilla-services/autopush/compare/1.19.0...1.19.1
https://github.com/mozilla-services/autopush/compare/1.19.1...1.19.2
https://github.com/mozilla-services/autopush/compare/1.19.2...1.19.3

TAGS
https://github.com/mozilla-services/autopush/releases/tag/1.19.3
https://github.com/mozilla-services/autopush/commit/9aba5ddffd0e7546a10753735d5ab3251c10226c

CHANGELOG
<a name="1.19.3"></a>
## 1.19.3 (2016-10-17)


#### Bug Fixes

*   use hex formatted ChannelID strings for bridged connections (#709) ([8aa1a7eb](https://github.com/mozilla-services/autopush/commit/8aa1a7eb1266f792538723f35569ae13e0355adc))
*   kill websocket.Notification (#707) ([e564a974](https://github.com/mozilla-services/autopush/commit/e564a9746feafbb30f2548eef89889c172fc5bb6))
We'll be deploying this release to PROD tomorrow, Wed. 10/19 @9am PST
Assignee: nobody → oremj
Status: NEW → ASSIGNED
Component: Operations: Deployment Requests → Operations: Autopush
Depends on: 1311055
QA Contact: rpappalardo
on production pre-deployment:

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

curl -s 'https://updates.push.services.mozilla.com/health' | python -mjson.tool
{
    "clients": 0,
    "prod.autopush.routerv2": {
        "status": "OK"
    },
    "prod.autopush.storage": {
        "status": "OK"
    },
    "status": "OK",
    "version": "1.18.0"
}


curl -s 'https://updates.push.services.mozilla.com/status' | python -mjson.tool
{
    "status": "OK",
    "version": "1.18.0"
}
--------------------------------
SENTRY TEST
--------------------------------

MY IP: 52.206.211.218
{
    "code": 418,
    "errno": 999,
    "error": "Test Failure",
    "message": "FAILURE:Success",
    "more_info": "http://autopush.readthedocs.io/en/latest"
}


client_info	

{'ami_id': 'ami-5b79853b', 'authorization': [Filtered], 'message_ttl': '', 'remote_ip': '52.206.211.218', 'request_id': '5b819278-dee4-4a7e-b514-c204d7049ebf', 'uri': '/v1/err/crit', 'user_agent': 'curl/7.35.0'}
pre-production checks:

----------------------------
E2E-TESTS (PROD)
----------------------------

e2e-test page -- OK
https://mozilla-services.github.io/autopush-e2e-test

webpush_qa: VAPID + Android test page -- OK
https://jrconlin.github.io/Webpush_QA
pre-production checks:

----------------------------
API SCENARIO TESTS (PROD)
----------------------------

ap-loadtester
https://github.com/mozilla-services/ap-loadtester
* basic, api_test scenarios - OK
:oremj has deployed this to PROD
Status: ASSIGNED → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED
----------------------------
URL CHECKS (PROD)
----------------------------

curl -s 'https://updates.push.services.mozilla.com/health' | python -mjson.tool
{
    "clients": 0,
    "prod.autopush.routerv2": {
        "status": "OK"
    },
    "prod.autopush.storage": {
        "status": "OK"
    },
    "status": "OK",
    "version": "1.19.3"
}


curl -s 'https://updates.push.services.mozilla.com/status' | python -mjson.tool
{
    "status": "OK",
    "version": "1.19.3"
}
--------------------------------
SENTRY TEST (PROD)
--------------------------------

MY IP: 52.206.211.218
{
    "code": 418,
    "errno": 999,
    "error": "Test Failure",
    "message": "FAILURE:Success",
}

client_info	

{'ami_id': 'ami-1875ae78', 'authorization': [Filtered], 'message_ttl': '', 'remote_ip': '52.206.211.218', 'request_id': '2eb66a12-482f-4a1f-8681-c933e55d92a9', 'uri': '/v1/err/crit', 'user_agent': 'curl/7.35.0'}
----------------------------
E2E-TESTS: VAPID (+Android)
----------------------------

Additional E2E-test which includes VAPID, encryption:
https://jrconlin.github.io/Webpush_QA/

FF Desktop (Nightly 52.0a1 & Release 49.0.1)  -- OK
FF Android (Nightly 52.0a1 & Release 49.0) -- OK

known error (non-blocking): 
https://sentry.prod.mozaws.net/operations/autopush-prod/issues/358077/
to be demoted to warning:
https://github.com/mozilla-services/autopush/issues/715
----------------------------
API SCENARIO TESTING 
see: https://github.com/mozilla-services/ap-loadtester/
----------------------------

MULTI-SCENARIO (SOAK) TESTS

[1]. basic
[2]. api_test

Run for 30 mins (no tracebacks) - OK
----------------------------
E2E-TESTS
----------------------------

CONFIG:

(default) PROD config should be:
dom.push.serverURL = push.services.mozilla.com


PROFILE CACHE TEST -- OK

profile cache test (from previous release to current release) 


DESKTOP E2E PUSH TEST -- OK

setup:
start browser with new profile
open: about:config
set: dom.push.loglevel=debug (instead of 'off')
open: Tools > WebDeveloper > BrowserConsole
open: https://mozilla-services.github.io/autopush-e2e-test/
choose: "service-worker.js"
click: "register Service Worker"
click: "subscribe to push"
observe push registration in console
click: "Always Receive Notifications" (in pop-up window)

1. registration test

steps:
click: "XHR to webpush app-server"
observe: successful registration in console

2. message delivery test

setup:
set: Repeat = 2
set: Delay (seconds) = 15

steps:
click: "XHR to webpush app-server"
observe: 2 pop notifications 15 seconds apart
 
3. payload test

setup:
set: Title = PAYLOAD TEST
set: Body = BODY TEXT HERE
set: TTL = 360
set: Repeat = 4
set: Delay (seconds): 20

steps:
click: "XHR to webpush app-server"
observe:
should see delayed pop notifications with Title, Body specified

4. storage test

purpose: verify that a request is stored on autopush for delayed delivery

setup:
(same as 3 above)

steps:
click: "XHR to webpush app-server
wait for pop notification, then immediately close browser
wait 25 seconds
re-open browser
observe:
should see 3 more delayed messages delivered on browser restart
----------------------------
SUMMARY
----------------------------

all e2e,api scenario tests passing.

Verifying this release.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.