701934 - QA and deploy BrowserID train-2011.11.10 to production

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: WebOps: Labs, task)

Description

[Lloyd Hilaiel [:lloyd]]

NOTE: due to a blocker, this train will not roll to production on 2011.11.17 - but QA is requested as normal

ChangeLog including issues resolved: 
https://github.com/mozilla/browserid/blob/06efa1/ChangeLog#L1-22

[QA] Suggested areas of focus for QA:
  * full regression testing
  * verify closed bugs referenced in changelog
  * 'keep me signed in' feature - should be tested via myfavoritebooze.org (writeup on this specific feature to come)

[RELEASE ENGINEERING]:
  * dbwriter process added:
    * before pushing, add monit files required to run dbwriter - /etc/monit/start_dbwriter and /etc/monit.d/dbwriter
    * add DBWRITER_URL to /etc/monit/start_browserid
    * add a new line to /home/git/post-update (curl to 62900 code update)
    * add a new file to logrotate config /etc/logrotate.d/browserid
  * restart monit right at the end of the production deployment (when servers are restarted)

Comment 1

[James Bonacci [:jbonacci]]

QA picks up this Beta train for testing.

Verified the addition of a fourth process running on the server:
/usr/local/bin/node /home/browserid/code/bin/verifier
/usr/local/bin/node /home/browserid/code/bin/keysigner
/usr/local/bin/node /home/browserid/code/bin/dbwriter
/usr/local/bin/node /home/browserid/code/bin/browserid

Note the new process for dbwriter.

Checking versions:
Beta:
https://diresworb.org/ver.txt
06efa1b changelog for train-2011.11.10

Dev:
https://dev.diresworb.org/ver.txt
06efa1b changelog for train-2011.11.10

Prod:
https://browserid.org/ver.txt
67098c0 merge verifier hotfix into production

Note here the same ver.txt info for Dev and Beta.

Server heartbeat:
https://diresworb.org/__heartbeat__
ok

Logs:
1. Noting the addition of two more logs: dbwriter.log, dbwriter-error.log

2. Found exactly one line in the verifier-error.log: "verifying assertion".
Please verify that this is expected.

3. keysigner.log has started archiving

4. Not sure if dbwriter.log has started archiving, so will track this.

Nothing else new or significant to report at this time.

Comment 2

[Ioana (away)]

(In reply to Lloyd Hilaiel from comment #0)
>   * 'keep me signed in' feature - should be tested via myfavoritebooze.org
> (writeup on this specific feature to come)

There is no 'keep me signed in' option on myfavoritebooze.org, nor on beta.myfavoritebooze.org. 

On beta.myfavoritebooze.org there is a new option though: "Always sign in using this email". Is this it? If so, how is it supposed to work?

From what I've tried until now, this option did nothing. Besides this, when checking it and signing in, then signing out and opening the emails list dialog again, the option is unchecked.

Comment 3

[James Bonacci [:jbonacci]]

Comment 2 is now Issue 570.

Comment 4

[James Bonacci [:jbonacci]]

QA signs off on the 11/10 train in Beta.
The following Closed/Fixed items did not get verified.
We can move them to the next release:
==>  * 547: fix regression in tooltips (weren't showing contents)
==>  * 429: strip whitespace on email input
==>  * 244: crypto changes to support IE8
==>  * 544: fix tab ordering in UI
==>  * 552: chrome specific UI fixes
==>  * 553: better UI feedback when hovering over buttons
==>  * 509: improve log message error levels (be sparing with 'error')

Lloyd, please add those to the next ChangeLog