Closed
Bug 1142389
Opened 9 years ago
Closed 9 years ago
please deploy fxa-content, fxa-auth train-32 to production
Categories
(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)
Cloud Services
Operations: Deployment Requests - DEPRECATED
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jrgm, Assigned: ckolos)
Details
(Whiteboard: [qa+])
Chris, Apologies for the delay with l10n strings. Thanks for your patience. Please build a new production stack fxa-{auth,content}-server train-32 with these parameters: Content Server: AppVersion 0.32.0-2 PuppetConfigVersion 20150302232703 Auth Server: AppVersion 1.32.1-1 AppVersionAuthDb 0.32.0-1 AppVersionCustomsServer 0.6.0-1 PuppetConfigVersion 20150302232703 RPMs: fxa-content-server-svcops-0.32.0-2.x86_64.rpm fxa-auth-server-svcops-1.32.1-1.x86_64.rpm fxa-auth-db-server-svcops-0.32.0-1.x86_64.rpm fxa-customs-server-svcops-0.6.0-1.x86_64.rpm $ curl https://accounts.stage.mozaws.net/ver.json; echo; curl https://api-accounts.stage.mozaws.net/; echo; {"version":"0.32.0","commit":"467f33a36baba967834205b147d7aa2665db358f","l10n":"d0430a3881","tosPp":"baa82bfefb"} {"version":"1.32.1","commit":"16d68bfabf238349c2d52d0cef17a44f08006308"} Re: rollback: there is no impediment to rolling this release back, and if there are issues/concerns post-release, it can be reverted by switching back DNS to the previous stack.
Reporter | ||
Updated•9 years ago
|
Assignee: nobody → ckolos
Assignee | ||
Comment 1•9 years ago
|
||
deployed and cut.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•