Closed Bug 1318864 Opened 8 years ago Closed 8 years ago

Please deploy autopush 1.21.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

Including CHANGELOG from 1.21.1 (which wasn't deployed):

CHANGELOG
<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))
Assignee: nobody → oremj
Status: NEW → ASSIGNED
QA Contact: rpappalardo
We'll be deploying this release to PROD this coming Monday., 11/21 @1:30 pm PST
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.20.0"
}


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

{'ami_id': 'ami-1875ae78', 'authorization': [Filtered], 'message_ttl': '', 'remote_ip': '52.206.211.218', 'request_id': 'cfd8be20-a8f8-4f6c-9adf-89e22a2e02de', 'uri': '/v1/err/crit', 'user_agent': 'curl/7.35.0'}
--------------------------------
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
UPDATE: We'll be deploying this release to PROD today, 11/21 @1:00 pm PST.
All pre-deploy tests complete.  ready for deploy.
:oremj has deployed this to PROD
Status: ASSIGNED → RESOLVED
Closed: 8 years 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"
}

{'ami_id': 'ami-4154f821', 'authorization': [Filtered], 'message_ttl': '', 'remote_ip': '52.206.211.218', 'request_id': '51dd2525-7951-4ed2-87da-61665bed1b8c', '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
----------------------------
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 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)
----------------------------
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.