Please re-deploy autopush 1.21.2 to PRODUCTION w/ logging config changes

VERIFIED FIXED

Status

Cloud Services
Operations: Autopush
VERIFIED FIXED
a year ago
a year 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.20.0...1.21.0
https://github.com/mozilla-services/autopush/compare/1.21.0...1.21.1
https://github.com/mozilla-services/autopush/compare/1.21.1...1.21.2

TAGS
https://github.com/mozilla-services/autopush/releases/tag/1.21.2
https://github.com/mozilla-services/autopush/commit/97a6be7a345539bb7611a11f9954423be33f4e48

CHANGELOG
<a name="1.21.2"></a>
## 1.21.2 (2016-11-17)


#### Chore

*   tag 1.21.2 ([728f2606](https://github.com/mozilla-services/autopush/commit/728f2606b992c91de5df08cb370ca6bdbf392dc4))

<a name="1.21.1"></a>
## 1.21.1 (2016-11-17)


#### Bug Fixes

*   call defer methods with callables (#737) ([aff89047](https://github.com/mozilla-services/autopush/commit/aff8904791420c1c44c90f0c4c79a93fea105d6a))
This is a re-deploy of 1.21.2 to rollout logging config changes.
We'll be re-deploying this release to PROD today., Tues., 11/22 between 1pm - 2pm PST
Assignee: nobody → oremj
Status: NEW → ASSIGNED
QA Contact: rpappalardo
on PRODUCTION pre-deployment:

----------------------------
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.21.2"
}


curl -s 'https://updates.push.services.mozilla.com/status' | python -mjson.tool
{
    "status": "OK",
    "version": "1.21.2"
}
--------------------------------
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/http.html#error-codes"
}

client_info	

{'ami_id': 'ami-4154f821', 'authorization': [Filtered], 'message_ttl': '', 'remote_ip': '52.206.211.218', 'request_id': '5f002f00-350b-408f-9068-a5673ca0ccb2', 'uri': '/v1/err/crit', 'user_agent': 'curl/7.35.0'}
Depends on: 1319500
--------------------------------
SUMMARY (PRE-DEPLOY TESTS)
--------------------------------

URL, Sentry checks -- OK
e2e push page, VAPID (+Android) page (Nightly, Release), topics tests -- OK
API tests - basic, api_test, loadtest scenarios -- OK
:oremj has deployed this config change to PRODUCTION
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.21.2"
}


curl -s 'https://updates.push.services.mozilla.com/status' | python -mjson.tool
{
    "status": "OK",
    "version": "1.21.2"
}
--------------------------------
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/http.html#error-codes"
}



client_info	

{'ami_id': 'ami-96e34cf6', 'authorization': [Filtered], 'message_ttl': '', 'remote_ip': '52.206.211.218, 172.31.45.160', 'request_id': 'aee9da3f-de68-4825-8f87-bbe363555008', '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)  -- OK
FF Android (Nightly, Release) -- OK
--------------------------------
E2E TEST: TOPICS
--------------------------------

Additional E2E-test which includes testing of notification bundling for stored messages
https://github.com/jrconlin/topics - follow README

Desktop (Nightly).  -- OK!
Android -- Not Yet Implemented (per :jrconlin)
----------------------------
E2E-TESTS
----------------------------

setting STAGE config to:
dom.push.serverURL = autopush.stage.mozaws.net

DESKTOP E2E PUSH TEST

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
----------------------------
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
----------------------------
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.