Closed Bug 1447084 Opened 7 years ago Closed 7 years ago

Please deploy autopush 1.42.0 to PRODUCTION

Categories

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

task
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: grumpy, Assigned: oremj)

References

Details

Please deploy autopush v1.42.0 to PRODUCTION Features add megaphone integration tests ([b2132f6](https://github.com/mozilla-services/autopush/commit/ b2132f6), closes [#1129](https://github.com/mozilla-services/autopu sh#1129)) add megaphone API query and repeating service updating ([cb21dc9](https://github.com/mozilla-se rvices/autopush/commit/cb21dc90f9f49133f441d299c5305509bbbcda37)) add megaphone broadcast handling, ping check, server tracking ([1fe4eeb](https://github.com/moz illa-services/autopush/commit/1fe4eebdcd5a7d4ed6134f46ea2c470ec2c01326)) add megaphone service change tracker ([ec13155](https://github.com/mozilla-services/autopush/co mmit/ec13155b3f1f24b2b06e93837c534f552b3c2648)) Refactor rearrange/hack back to 100% coverage ([80e79b0](https://github.com/mozilla-services/autopush/co mmit/80e79b0e93c719bf0dafd979fb4e978d879ff868), closes [#1143](https://github.com/mozilla-services/a utopush#1143)) Bug Fixes add missing setup_module() function to test_db ([3266888](https://github.com/mozilla-services/a utopush/commit/32668884c834320d77ac03b3b05ae0acb54459ac), closes [#1157](https://github.com/mozilla- services/autopush#1157)) Add ClientError handler to UnregisterCommand ([9b99c28](https://github.com/mozilla-services/aut opush/commit/9b99c2851ac5237373ec8615a570c9d04c867df9)) Handle PotentialDataLoss error ([7f60f82](7 f60f8278641a6bfea53c30fdb17dbc4f44e7777), closes [#1151](https://github.com/mozilla-services/autopus h#1151)) remove GCM collapse key ([65f1003](65f1003 0d6da4bd0765a0d5a540ffc773c8d9f8), closes [#1149](https://github.com/mozilla-services/autopush/issue s/1149)) fix _expiry() function to use seconds ([cfcad77](https://github.com/mozilla-services/autopush/c ommit/cfcad77acf5e73178cfd2a3f289ab2d59781401e), closes [#1073](https://github.com/mozilla-services/ autopush#1073))
Assignee: nobody → oremj
QA Contact: chartjes
Depends on: 1447083
URL AND SENTRY CHECKS (PROD PRE-DEPLOY) pytest -v --testrail --tr-config=tests/testrail.cfg --api-version=1.41.0 --env=production tests/test_urls.py tests/test_sentry.py [testrail] New testrun created with name "autopush-qa" and ID=8918 tests/test_urls.py::test_status_endpoint PASSED tests/test_sentry.py::test_generate_logcheck_error PASSED[testrail] Start publishing [testrail] Testcases to publish: 10691, 10692 [testrail] End publishing Sentry reports the following details: {'ami_id': 'ami-6d871315', 'authorization': [Filtered], 'message_ttl': None, 'python_version': '2.7.13 (84a2f3e6a7f8, Oct 03 2017, 11:00:55) [PyPy 5.9.0 with GCC 6.2.0 20160901]', 'remote_ip': '108.160.90.26, 172.31.42.55', 'request_id': 'e415d066-04c7-4c72-a401-c4f4d30c47f2', 'uri': '/v1/err/crit', 'user_agent': 'python-requests/2.14.2'} whatmyip.com reports my IP address as 108.160.90.26
E2E-TESTS: VAPID (+Android PRE-DEPLOY) Additional E2E-test which includes VAPID, encryption: https://jrconlin.github.io/Webpush_QA/ FF Android (Nightly, Release) -- OK
DESKTOP E2E PUSH TEST Install Docker, grab the image firefoxtesteng/autopush-e2e-test and then start the container using the command: docker run -p 8201:8201 firefoxtesteng/autopush-e2e-test Using a fresh profile for Firefox, go to to http://localhost:8201 * go to about:config and set dom.push.serverURL = wss://push.services.mozilla.com/ Test #1 * with 'service-worker.js' selected click on 'Register Service Worker' and see the messages: registering service worker registered service worker. scope: http://localhost:8201/ * alter the 'Title' and 'Body' fields in the Notifications Property form to unique values * click on 'pop Notification' and verify the notification contains your expected Title and Body * click on 'close Notification' and verify the notification is closed Test #2 * click on 'subscribe to push' * change values for 'repeat' and 'delay' to have at least 2 messages with at least 5 seconds between them * click on 'XHR to webpush app-server' and verify the number of messages sent and the delay between them is accurate Passes on PROD prior to deployment
iOS: SYNC + FxA + PUSH TEST SETUP - Get account for buddybuild (from: njpark) - Download “TestFlight” app - Receive invite to use, enter code - Get latest Beta Build (“click Update, if needed”) - Create new FxA accounts (against PROD FxA server) - Login to FxA account with a fresh Firefox profile - Save some bookmarks and create some navigation history TEST STEPS (STR) - Go to settings in new download of Firefox iOS app - Login to new FxA (PROD) account - wait or force sync activity - Observe bookmarks and history appear in Firefox browser RESULTS - bookmark sync - OK - history sync - OK
TOPIC SERVER Follow directions at https://github.com/jrconlin/topics using new profile in Firefox desktop release. PASSED in pre-deployment testing
QA validates the current production environment, okay for production push later today.
URL AND SENTRY TESTING POST-DEPLOY pytest -v --testrail --tr-config=tests/testrail.cfg --api-version=1.41.0 --env=production tests/test_urls.py tests/test_sentry.py [testrail] New testrun created with name "autopush-qa" and ID=8920 tests/test_urls.py::test_status_endpoint PASSED tests/test_sentry.py::test_generate_logcheck_error PASSED[testrail] Start publishing [testrail] Testcases to publish: 10691, 10692 [testrail] End publishing Sentry returned the following information: {'ami_id': 'ami-e8e67a90', 'authorization': [Filtered], 'message_ttl': None, 'python_version': '2.7.13 (84a2f3e6a7f8, Oct 03 2017, 11:00:55) [PyPy 5.9.0 with GCC 6.2.0 20160901]', 'remote_ip': '108.160.90.26, 172.31.11.204', 'request_id': '4d502799-4942-4561-b841-36b3265e2e7c', 'uri': '/v1/err/crit', 'user_agent': 'python-requests/2.14.2'} whatsmyip.com reports my IP address as being 108.160.90.26 PASSES post-deploy
A bug was found during the VAPID testing, with older clients reporting "Error retrieving push subscription". The autopush developers discovered the bug causing this message. Decision was made to roll back the deployment, skip this current update cycle and release patched code during the next deployment cycle.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
Depends on: 1450947
No longer depends on: 1450947
You need to log in before you can comment on or make changes to this bug.