Closed Bug 1181757 Opened 9 years ago Closed 9 years ago

please deploy fxa-{content,auth,oauth,profile} train-40 to production

Categories

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

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jrgm, Assigned: jrgm)

References

Details

(Whiteboard: [qa+])

Please promote these stacks to production:

fxa-a-s-train-40-132
fxaTrain:                 train-40
fxa_auth_serverGitRef:    refs/tags/v1.40.0
fxa_auth_db_serverGitRef: refs/tags/v0.40.0
fxa_customs_serverGitRef: refs/tags/v0.39.0
SvcopRef:                 6f2f7a6c1c4785e4d07d574fb11c01c4b7b2e6dd
PuppetGitRef:             refs/tags/20150626214007-1

fxa-c-s-train-40-139
fxaTrain:                 train-40
fxa_content_serverGitRef: refs/tags/v0.40.0
SvcopRef:                 6f2f7a6c1c4785e4d07d574fb11c01c4b7b2e6dd
PuppetGitRef:             refs/tags/20150626214007-1

Expected versions:

{"version":"0.40.0","commit":"726a047b79daf6ec52b893bd7acfd65525fc9ae4","l10n":"86056510dd","tosPp":"d40365ec45"}
{"version":"1.40.0","commit":"affb4e6da95e61b3943f96b9ad74ae2b17de19ba"}
{
  "version": "0.39.0",
  "commit": "fe7b0359e35ad36857ad363fe0a8068941da1b21"
}
{
  "version": "0.39.0",
  "commit": "b50a9140a2648bf2d324addcfa0348c3e748b036"
}
So, my bad choice. There is a migration in train-40 that removes some obsolete stored procedures. In the interests of time, I was going to defer that, but train-40 insists on the migration number being bumped. So I will do the migration tomorrow morning and then put train-40 live.
Depends on: 1181875
So I got caught up in a couple of things and am basically out of time for today. The prod stacks are built and I ran a quick smoketest. I will re-warm the auth-server and switch DNS to these stacks first thing tomorrow.
Okay, switched fxa-auth at 12:36PDT and fxa-content at 13:14PDT. Looks fine.

$ sh checkver-prod.sh 
{"version":"0.40.0","commit":"726a047b79daf6ec52b893bd7acfd65525fc9ae4","l10n":"86056510dd","tosPp":"d40365ec45"}
{"version":"1.40.0","commit":"affb4e6da95e61b3943f96b9ad74ae2b17de19ba"}
{
  "version": "0.39.0",
  "commit": "fe7b0359e35ad36857ad363fe0a8068941da1b21"
}
{
  "version": "0.39.0",
  "commit": "b50a9140a2648bf2d324addcfa0348c3e748b036"
}
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.