Closed
Bug 1104186
Opened 10 years ago
Closed 10 years ago
please deploy fxa-content train-26 and fxa-auth train-24 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, Please build a new production stack fxa-content-server train-26 with these parameters: Content Server: AppVersion 0.26.2-1 ProvisioningVersion 20141120194104 Auth Server: auth AppVersion 1.24.1-1 AppVersionAuthDb 0.23.0-1 *** NOTE: must not be 0.24 AppVersionCustomsServer 0.5.0-1 ProvisioningVersion 20141113194804 NOTE: this release is not changing the version of fxa-auth-db-server that is in production. It will continue to use the one without stored procedures. The change in fxa-auth-server is simply to return a uid with /session/status and nothing else. RPMS: fxa-auth-server-svcops-1.24.1-1.x86_64.rpm fxa-content-server-svcops-0.26.2-1.x86_64.rpm $ curl https://accounts.stage.mozaws.net/ver.json; echo; curl https://api-accounts.stage.mozaws.net/; echo; {"version":"0.26.2","commit":"35506007acf6e94a3c25000aad67d97b1c761eab","l10n":"4168ef3cb7","tosPp":"328cbfec53"} {"version":"1.24.1","commit":"1f8a2412e8eac14ab4ab674637a9fef2fd6c7fc8"}
Reporter | ||
Comment 1•10 years ago
|
||
Note on 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 | ||
Comment 2•10 years ago
|
||
this went live about 12:30 PST and no substantial issues noted
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•