Closed Bug 1012773 Opened 12 years ago Closed 12 years ago

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

Categories

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

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jrgm, Assigned: jrgm)

Details

(Whiteboard: [qa+])

Please tag train-13 for fxa-auth and fxa-content (and fxa-auth-db-server). Notes: 1. we will respin the rpm for fxa-content to pick up further l10n content changes (strings-only) next week before going to production. 2. we also need to work out a tagging/release pattern for fxa-auth-db-server, which builds a a separate rpm.
fix summary to 'please deploy fxa-content and fxa-auth train-13 to stage'
Summary: please deploy fxa-content and fxa-auth train-12 to stage → please deploy fxa-content and fxa-auth train-13 to stage
https://github.com/mozilla/fxa-auth-server/tree/train-13 cda9a41ce6a824994e7f77ef89a94e554ea37d00
I built rpms and stacks fxa-s-a-8 and fxa-s-c-3 for these shas and I have switched DNS in stage over to them: $ curl https://api-accounts.stage.mozaws.net/; echo {"version":"0.13.0","commit":"cda9a41ce6a824994e7f77ef89a94e554ea37d00"} $ curl https://accounts.stage.mozaws.net/ver.json; echo {"version":"0.13.0","commit":"829ee706ff40f2c1c37040bb2c0643a21cc21b8f"} Also, fxa-auth-db-server was built as an rpm at sha 702824003fbfbdd7d011d0c5fbfa0d018fde9f0e and is running on the auth server stack fxa-s-a-8
Did this finish? I am having some issues hitting FxA-Auth Stage. I keep getting 500s back from the quick test and load test
Status: NEW → ASSIGNED
Whiteboard: [qa+]
I have been testing failure paths (forcing network problems and such) so it has been up and down. I will be replacing the current stack in a while with one with fixes, but I will need to trigger some failures again. Do you want me to defer that to later?
Actually, I will do the destructive tests on a different stack.
:jrgm - no problem. I was just running a comparison of load tests for our repos. All done for this week. Break away.... :-)
I rebuilt the rpm for fxa-content-server to pick up changes in fxa-content-server-l10n (and in https://github.com/mozilla/legal-docs) and built a new stack fxa-s-c-4 with it using puppet version 20140527185703. The l10n and legal changes involve content changes for es_AR, ff, ja, pt and changes to translations of privacy for cs, de, el, es, hr, hu, it, pl, pt_BR, ru, sr_Latn, zh_CN, and to terms for es. I also built a new stack with the same rpms for fxa-auth-server with puppet version 20140d52718503, which will set the backend to 'mysql' (not 'httpd').
Okay, tests pass with either backend mysql or httpdb. We'll be starting in prod with backend mysql and at an appropriate time, get some mileage with the httpdb backend.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Summary: please deploy fxa-content and fxa-auth train-13 to stage → please deploy fxa-content and fxa-auth train-13 to production
Summary: please deploy fxa-content and fxa-auth train-13 to production → please deploy fxa-content and fxa-auth train-13 to stage
You need to log in before you can comment on or make changes to this bug.