Closed Bug 1299907 Opened 8 years ago Closed 8 years ago

Please deploy autopush 1.17.2 to PRODUCTION

Categories

(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)

task
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: cloud-services-qa, Assigned: oremj)

References

Details

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

COMPARISONS
https://github.com/mozilla-services/autopush/compare/1.16.1...1.17.0
https://github.com/mozilla-services/autopush/compare/1.17.0...1.17.1
https://github.com/mozilla-services/autopush/compare/1.17.1...1.17.2

TAGS
https://github.com/mozilla-services/autopush/releases/tag/1.17.2
https://github.com/mozilla-services/autopush/commit/b313e6e438573ffa525ae039d6b75581070bcba9

CHANGELOG
<a name="1.17.2"></a>
## 1.17.2 (2016-08-31)


#### Test

*   clarify where we mean IRouter vs db.Router ([33244055](https://github.com/mozilla-services/autopush/commit/332440558bef35668873307cebe390b714b6e467))

#### Chore

*   break out base deps into their own req file ([001e0da4](https://github.com/mozilla-services/autopush/commit/001e0da4d2cc87b578b01261db09f3925f0a8503))
*   git mv a break out of the base deps ([abc63330](https://github.com/mozilla-services/autopush/commit/abc633307466e9731b2a2f2ee7d49b50ee6de8e0))

#### Bug Fixes

*   provide better logging and fix UAID misreference ([704fd814](https://github.com/mozilla-services/autopush/commit/704fd81469e41ef5da522fff27fa1aae235c0bd4))
*   do not try to JSON serialize log output ([9861edb6](https://github.com/mozilla-services/autopush/commit/9861edb6f8ec506130591b4b5a13dbb16a1b2a52))
*   clarify token references in HTTP endpoint docs ([8a751472](https://github.com/mozilla-services/autopush/commit/8a7514721abc8d16bd487c1ef4560c5c5dfe9ba3))
*   add URI to error messages to aid in bad senderIDs ([05e5d00f](https://github.com/mozilla-services/autopush/commit/05e5d00f8b3974139a54310255ce4ef0a2cf6c7b))
*   kill dead_cache, it's no longer used ([2135dd8b](https://github.com/mozilla-services/autopush/commit/2135dd8b99b07798f7bb41ed15b6daf582feda32))
*   update Makefile to use correct requirements ([ec6418b3](https://github.com/mozilla-services/autopush/commit/ec6418b3183faf1ff94bfea537fcb981e4cb4494))
*   handle more errors to connection nodes ([3cc24fe8](https://github.com/mozilla-services/autopush/commit/3cc24fe876e47115cbe2993216d6e80a585f4a8e))
*   disable log_exception capturing in tests ([62074f74](https://github.com/mozilla-services/autopush/commit/62074f74f45b36afd8fa20f549a41ca6285fa398))
*   trap UnicodeEncodeError ([a116def7](https://github.com/mozilla-services/autopush/commit/a116def7bfbeb087bc80845dd2eda438515b3ccb), closes [#606](https://github.com/mozilla-services/autopush/issues/606))

#### Features

*   dependency update ([03ba5b56](https://github.com/mozilla-services/autopush/commit/03ba5b56c39d3d99ff317c0f08ade929b23652f9), closes [#639](https://github.com/mozilla-services/autopush/issues/639))
*   add docker-compose and revamp docs ([b4fb7c67](https://github.com/mozilla-services/autopush/commit/b4fb7c6771940f5c2067ba03895bd86186dd2c1b), closes [#559](https://github.com/mozilla-services/autopush/issues/559))
*   reduce warnings in code base ([a2308b99](https://github.com/mozilla-services/autopush/commit/a2308b99edbab0117bb7074f2b32b8eaf8f9beda))

#### Refactor

*   extract a simple BaseHandler ([a794e20f](https://github.com/mozilla-services/autopush/commit/a794e20fa82075d72644d0f358951cb5d0fed17b))
*   cleanup of Handler initialize/ap_settings ([031e1446](https://github.com/mozilla-services/autopush/commit/031e1446df485aab834a7664e67612d4d1920f8e))
Assignee: nobody → oremj
Status: NEW → ASSIGNED
QA Contact: mbrandt
We will be deploying this release to PRODUCTION today, Thursday 9/1 @ 1:30pm PST.
here's what's 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.17.1"
}

curl -s https://updates.push.services.mozilla.com/status | python -mjson.tool
{
    "status": "OK",
    "version": "1.17.1"
}
e2e-tests pre-deployment...

----------------------------
E2E-TEST (PROD)
----------------------------

ap-loadtester: basic scenario - OK
e2e-test: Push Test Page - OK
:oremj has promoted 1.17.2 to production.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
PRODUCTION post-deployment...
here's what's 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.17.2"
}


curl -s https://updates.push.services.mozilla.com/status | python -mjson.tool
{
    "status": "OK",
    "version": "1.17.2"
}
PRODUCTION post-deployment …

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

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://people.mozilla.org/~ewong2/push-notification-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 = 120
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

5. storage test with message flood

purpose: verify that a "flood" of requests are stored on autopush for delayed delivery

setup:
(same as 3 above)
only set Flood Delay (this will trigger notification flood behavior)

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
Additional E2E-test which includes VAPID, encryption:
https://jrconlin.github.io/Webpush_QA/

Tested on Desktop Nightly and Android - PASSED
----------------------------
SENTRY ERROR CHECK
----------------------------

Check if Sentry is working - PASSED

PROD
https://updates.push.stage.mozaws.net/v1/err/crit

NOTE:
error messages on Sentry were delayed by approx. 1 hr probably due to backup of 500s

----------------------------
E2E-TESTS: VAPID/Android
----------------------------

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

Run on desktop (Nightly) and on Android - PASSED
----------------------------
SUMMARY
----------------------------

All e2e-tests and api scenario tests (basic, api_test) passing.

* ap-loadtester: basic & api_test scenarios - OK
* e2e-test: findmydevice, FirefoxHello & Push Test Page - OK


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