QA and deploy BrowserID train-2011.10.27 to production

VERIFIED FIXED

Status

VERIFIED FIXED
7 years ago
2 years ago

People

(Reporter: lloyd, Assigned: jbonacci)

Tracking

Details

(Reporter)

Description

7 years ago
ChangeLog including issues resolved: 
https://github.com/mozilla/browserid/blob/7ee8325/ChangeLog#L1-12

[QA] Suggested areas of focus for QA:
  * normal regression testing
  * verify closed bugs referenced in changelog

[RELEASE ENGINEERING]:
  * heartbeat URL is changed!  update monit scripts! (s/ping.txt/__heartbeat__/)
    + first update files /etc/monit.d/{browserid,verifier}
    + at the time you push, restart monit
    + if done carefully, downtime is still <= 2s
  * schema is changed!  there's an sql update script that is riding the train that should be run *after* the update is live (on the hot database) - https://github.com/mozilla/browserid/commit/5685d46427d5155fd67bd3256c3ac71cb4e2de24
(Reporter)

Updated

7 years ago
Assignee: server-ops-labs → jbonacci
No longer depends on: 694383
QA Contact: zandr → jbonacci
(Assignee)

Comment 1

7 years ago
/me notes that the hearbeat URL is now: https://diresworb.org/__heartbeat__
(Assignee)

Comment 2

7 years ago
Code and Deployment Verification:

Processes on browserid-stage1.vm1.labs.sjc1.mozilla.com:
www-data 14027  0.0  1.4 631352 14712 ?        Sl   Oct27   0:40 /usr/local/bin/node /home/browserid/code/verifier/run.js
www-data 15362  0.1  2.0 636424 21236 ?        Sl   11:41   0:39 /usr/local/bin/node /home/browserid/code/browserid/run.js

Versions:
Beta:
https://diresworb.org/ver.txt
7ee8325 changes in train-2011.10.27

Dev:
https://dev.diresworb.org/ver.txt
b226767 bump to postprocess 0.0.3 - fixes issues in postprocessing certain types of responses 
(where a string is sent() instead of a buffer as the first chunk)

Prod:
https://browserid.org/ver.txt
1528364 if rp doesn't provide scheme or port, then ignore them in testing for audience match: issue #500


Server heartbeat:
https://diresworb.org/__heartbeat__
ok
(Assignee)

Updated

7 years ago
Status: NEW → ASSIGNED
(Assignee)

Comment 3

7 years ago
+ Ioana
(Assignee)

Comment 4

7 years ago
OK. All Closed/Fixed issues have been verified.
For the next 3 days, QA will focus on breath of coverage with special efforts on the following (in order of priority):
iOS4 and iOS5
Older Android devices (firmware version < 3.0)
Various flavors of Linux
IE9
(Assignee)

Comment 5

7 years ago
I am really concerned about the following issue:
511: BrowserID popup persists after logging in

Blocking this train until we can discuss it in more detail during Thursday's BrowserID bug triage.
(Assignee)

Comment 6

7 years ago
Dev and QA have been able to duplicate the issue described in Issue 511.
This is no longer a blocker.

But, we have a new blocker for the current Beta:
525: The user is not always logged in when using BrowserID

QA to spend Thu into Friday to try to duplicate this issue and document it for a Friday morning triage and go/no go decision on this train.
(Assignee)

Comment 7

7 years ago
We are no longer blocked on 511 and 525. QA signs off on this train on Beta.
Status: ASSIGNED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
beginning production deployment...
train-2011.10.27 now live in production.
(Assignee)

Comment 10

7 years ago
Verified 10/27 train to Production:
44ff6a9 integrating train 2011.10.27

Quick tests look good on myfavoritebeer.org and browserid.org
Status: RESOLVED → VERIFIED

Updated

7 years ago
Blocks: 699962

Updated

7 years ago
Blocks: 701934

Updated

7 years ago
No longer blocks: 701934
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.