please deploy fxa-content and fxa-auth train-19 to stage

RESOLVED FIXED

Status

Cloud Services
Operations: Deployment Requests
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: jrgm, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [qa+])

(Reporter)

Description

4 years ago
Please create train-19 branches for fxa-content-server and fxa-auth-server. I'll take care of fxa-auth-db-server and fxa-customs-server. Thanks.
https://github.com/mozilla/fxa-auth-server

4796d08549e3da03da9fafc9f433fa22f9b6cc0d
https://github.com/mozilla/fxa-content-server

08ac81271b320b5a7dba9973576fffce118a71c9
(Reporter)

Comment 3

4 years ago
I built stacks fxa-s-{a,c}-6 in stage and switched DNS to them. Tests are passing. Still waiting on a config change in puppet for enabling Ukranian. 

$ curl https://accounts.stage.mozaws.net/ver.json; echo; curl https://api-accounts.stage.mozaws.net; echo;
{"version":"0.19.0","commit":"08ac81271b320b5a7dba9973576fffce118a71c9","l10n":"665ef9d273","tosPp":"1dd2411a2b"}
{"version":"1.19.0","commit":"4796d08549e3da03da9fafc9f433fa22f9b6cc0d"}
We recently found this bug in the Sync re-auth flow in production: https://github.com/mozilla/fxa-content-server/issues/1549

We're confident that it's fixed in the train-19, so it may be nice to accelerate the deployment of that.
OTOH, there's no evidence that the number of affected users is large (it only affects the sync re-auth flow and there's a manual way to recover), so I'd be wary taking on additional risk by shipping train-19 before you guys feel comfortable with it.
(Reporter)

Comment 6

4 years ago
So, usually we are waiting to give localizers time to complete their updates. How much do we leave untranslated if we don't wait this time. 

(I'm generally good with this train, just wanted to check some database related stuff).
(Reporter)

Comment 7

4 years ago
Okay all done. Note: not respinning rpm to pick up (one day) of l10n changes.

See https://bugzilla.mozilla.org/show_bug.cgi?id=1053556
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.