1104200 - please deploy fxa-oauth and fxa-content train-26 to production

Status: RESOLVED FIXED

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

Description

[John Morrison [:jrgm]]

Chris,

Please build production stacks for fxa-oauth-server and fxa-profile-server with these paramenters:

OAuth Server:
AppVersion                  0.26.2-1
PuppetConfigVersion         20141120194104

Profile Server:
AppVersion                  0.26.1-1
PuppetConfigVersion         20141119191704

RPMS:
  fxa-oauth-server-svcops-0.26.2-1.x86_64.rpm
  fxa-profile-server-svcops-0.26.1-1.x86_64.rpm

$ curl https://oauth.stage.mozaws.net/; echo; curl https://profile.stage.mozaws.net/; echo;
{
  "version": "0.26.2",
  "commit": "ab2b48dd505fb0f260ea6803efa7a4d3cc19d5de"
}
{
  "version": "0.26.1",
  "commit": "275e2d0cbe43a5a099cf9ce18aee63bb542bbed9"
}

Comment 1

[John Morrison [:jrgm]]

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.

Comment 2

[John Morrison [:jrgm]]

Further note, the logging format has changed for fxa-oauth and fxa-profile in this train. Changes to heka and decoders and fxa puppet-config were worked out and tested in stage, and should Just Work™ but we should probably coordinate with :whd.

Comment 3

[Wesley Dawson [:whd]]

I need to set up temp message matchers on the prod aggregator so we accept both old format and new format, and will coordinate with :ckolos to make sure this is live before the deploy. After the deploy I'll re-puppetize and drop the old format.

Comment 4

[John Morrison [:jrgm]]

this went live about 12:30 PST and no substantial issues noted