Closed
Bug 1038367
Opened 10 years ago
Closed 10 years ago
please deploy fxa-content and fxa-auth train-17 to stage
Categories
(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)
Cloud Services
Operations: Deployment Requests - DEPRECATED
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: jrgm, Assigned: jrgm)
Details
(Whiteboard: [qa+])
Please tag train-17 for fxa-auth and fxa-content (and fxa-auth-db-server). Note: we will respin the rpm for fxa-content to pick up further l10n content changes (strings-only) *next week* before going to production. Note for ckolos (and others): This train requires a column to be added to the fxa.accounts table. This will be a trivial cost in stage (relatively small number of accounts) but may be a non-trivial cost in production. I will be create an RDS in stage with dummy data for the same order of magnitude of production data and get a sense of what kind of cost this will be (mysql 5.6 is nominally much better with schema DDL changes than previous versions, which were well known to be horror shows). Will talk with you about this later.
Assignee | ||
Comment 1•10 years ago
|
||
Changing 16 -> 17, in the summary line.
No longer depends on: 1032386
Summary: please deploy fxa-content and fxa-auth train-16 to stage → please deploy fxa-content and fxa-auth train-17 to stage
Comment 2•10 years ago
|
||
https://github.com/mozilla/fxa-content-server/tree/train-17 6ebda2aed5e0670de6d198aff6de8edfc61764f5
Comment 3•10 years ago
|
||
https://github.com/mozilla/fxa-auth-server/tree/train-17 930a5881a18ef667e6908d639ff3aa328aa74576 https://github.com/mozilla/fxa-auth-db-server/tree/train-17 45cd33fabe0a496025b013f5b81218d2b21a8281
Assignee | ||
Comment 4•10 years ago
|
||
I built rpms and stacks and have switched dns to use them (after running remote tests against them). $ curl https://accounts.stage.mozaws.net/ver.json; echo ; curl https://api-accounts.stage.mozaws.net/; {"version":"0.17.0","commit":"6ebda2aed5e0670de6d198aff6de8edfc61764f5","l10n":"5baeb4c948", "tosPp":"f971f5919e"} {"version":"0.17.0","commit":"930a5881a18ef667e6908d639ff3aa328aa74576"} I have some failing selenium tests that I'll dig into now; they are not major, but one that is failing is `legal` which is for the corrected tos and pp content/url - they don't look like they should be failing, but they are. More later.
Assignee | ||
Comment 5•10 years ago
|
||
I built new stacks and rpm to pick up l10n changes, the fix for lsb and hsb (Upper/Lower Sorbian), and fix for some heka configuration $ curl -s 'https://accounts.stage.mozaws.net/ver.json'; echo {"version":"0.17.1","commit":"e445b4e463fff4394b9ecf5e209bfbf270ea56f6","l10n":"c73b78e17a","tosPp":"14ef644ae0"} $ curl -s 'https://api-accounts.stage.mozaws.net/'; echo {"version":"0.17.0","commit":"930a5881a18ef667e6908d639ff3aa328aa74576"} Puppet-config version: 20140721222516
Assignee | ||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•10 years ago
|
Status: RESOLVED → VERIFIED
Resolution: FIXED → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•