926633 - please deploy browserid-bigtent stacks to stage (to address an over-restrictive pattern match).

Status: VERIFIED FIXED

(Cloud Services :: Server: Identity, defect)

Description

[John Morrison [:jrgm]]

I've built an rpm for browserid-bigtent on the
train-2013.05.29-hotfix-9-24v3 branch (which is what is now in
production, minus a small update for a pattern match of claimed_id).

output rpm on r6:
/home/jrgm/workspace-browserid-bigtent-0.2013.05.29-6.el6_116978/browserid-bigtent/rpmbuild/RPMS/x86_64/browserid-bigtent-0.2013.05.29-6.el6_116978.x86_64.rpm

Build command:
sh -x ./build.sh browserid-bigtent train-2013.05.29-hotfix-9-24v3 a227e0bf857abb4e4cb8bad3740eb87ae0a12854 116978

md5sum of rpm: bba8af4d0c536844cd199039653b2964

Gene, please build a stack in stage with the above rpm. We will only ultimately shipping the bigtent part of these stacks to address https://github.com/mozilla/browserid/issues/3949

Comment 1

[Gene Wood [:gene]]

Staging stack 1014 built (this is a stack only containing bridge-yahoo, not persona and bridge-gmail) and staging DNS has been pointed to it.

Comment 2

[John Morrison [:jrgm]]

Hey, Gene. Thanks. I have a couple of other things to check, but can you proceed to build the production stacks with this rpm? I can work with bwong to change over the DNS, and not keep you waiting late.

Comment 3

[Gene Wood [:gene]]

Done. Stack 1015 is up in both prod datacenters. It's just bigtent.

Comment 4

[John Morrison [:jrgm]]

Okay, QA signs off on this. I'll add instructions to bug 926995 for Ben to update DNS to the 1015 stack CNAME's.