Closed
Bug 1201658
Opened 10 years ago
Closed 10 years ago
please deploy fxa-{content,auth,oauth,profile} train-44 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: jrgm)
Details
(Whiteboard: [qa+])
Please deploy fxa-{content,auth,oauth,profile} train-44 to production.
fxa-c-s-train-44-177
fxaTrain: train-44
fxa_content_serverGitRef: refs/tags/v0.44.0
SvcopRef: 5ecc54aaba34a6ed83c66979d0b3c002396b634d
PuppetGitRef: 6fae2235bb3530c2d106b7d767ea7154fd740eb4
NOTE: v0.44.0, not v0.44.1, which can happen later
fxa-o-s-train-44-153
fxaTrain: train-44
fxa_oauth_serverGitRef: refs/tags/v0.44.0
verifierGitRef: 0497a36c
SvcopRef: 5ecc54aaba34a6ed83c66979d0b3c002396b634d
PuppetGitRef: 6fae2235bb3530c2d106b7d767ea7154fd740eb4
fxa-p-s-train-44-98
fxaTrain: train-44
fxa_profile_serverGitRef: refs/tags/v0.44.0
SvcopRef: 5ecc54aaba34a6ed83c66979d0b3c002396b634d
PuppetGitRef: 6fae2235bb3530c2d106b7d767ea7154fd740eb4
fxa-a-s-train-44-169
fxaTrain: train-44
fxa_auth_serverGitRef: refs/tags/v1.44.0
fxa_customs_serverGitRef: refs/tags/v0.39.0
fxa_auth_db_serverGitRef: refs/tags/v0.44.0
SvcopRef: 5ecc54aaba34a6ed83c66979d0b3c002396b634d
PuppetGitRef: 6fae2235bb3530c2d106b7d767ea7154fd740eb4
Expected versions:
{"version":"0.44.0","commit":"6431a6bda1704434ac4a8bda47239f196fb0a00b","l10n":"b365a06533","tosPp":"bc68fb4d01","source":"https://github.c\
om/mozilla/fxa-content-server.git"}
{"version":"1.44.0","commit":"487830e9040bd131fb3ec24a8b920d7dacaccc08"}
{
"version": "0.44.0",
"commit": "e31f764c6dcfaeecc8e0ac531002eeab279137ea"
}
{
"version": "0.44.0",
"commit": "040b41e1cc6403d89b8130c7a022687fac57f5d7"
}
| Assignee | ||
Comment 1•10 years ago
|
||
Had a typo on the region for fxa-profile sqs. Re-deploying with svcops:refs/head/fxa-train-44-fix-profile-sqs-arn-value
| Assignee | ||
Comment 2•10 years ago
|
||
oSorry, updated in #fxa, but not here. While deploying this Pocket happened to go down, and the profile-server stack ELB was assigned an IP that had been recently used by some other AWS customer, and so, was flooded with 404 requests. I decided to defer deployment until tomorrow a.m.
| Assignee | ||
Comment 3•10 years ago
|
||
I rolled back the fxa-auth-server train-44 due to heavy database I/O. So none of these new stacks are live at this moment. Will update with more details in a while. No user impact, aside from increased latency in fxa-auth requests while train-44 was live.
| Assignee | ||
Comment 4•10 years ago
|
||
Okay, there is an updated fxa-auth-server https://github.com/mozilla/fxa-auth-server/tree/v1.44.1
f0828c969cb0731af221ed27f7a3e8e17a7a8327, and I am building that stack in production to go live shortly.
| Assignee | ||
Comment 5•10 years ago
|
||
Building a new oauth-server v0.44.1 to put back disabling token expiration - https://github.com/mozilla/fxa-oauth-server/commit/6c8867a40040a85387c38493fb855ab8736f01ef
| Assignee | ||
Comment 6•10 years ago
|
||
Okay, fxa-{content,profile,oauth,auth} train-44 running in production.d
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 7•10 years ago
|
||
fxa-content-server v0.44.1 was set live about 2015-09-10 13:30 PDT.
You need to log in
before you can comment on or make changes to this bug.
Description
•