If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

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

VERIFIED FIXED

Status

Cloud Services
Server: Identity
--
critical
VERIFIED FIXED
4 years ago
4 years ago

People

(Reporter: jrgm, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

4 years ago
Hi Gene, can you build the production stacks with this rpm? (I can work with bwong to switch DNS, so you won't be working late). Thanks.

----

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
(Reporter)

Comment 1

4 years ago
Okay, QA signs off on switching DNS to the new 1015 production stacks.

Ben, 

Gene has built new stacks (1015) for yahoo.login.persona.org. 

On the bastion host for persona:
    $ for r in us-west-2 us-east-1; do get_hosts 1015 -e -r $r; done
    yahoo-login-persona-org-1015-1894173373.us-west-2.elb.amazonaws.com
    yahoo-login-persona-org-1015-60255593.us-east-1.elb.amazonaws.com

So, those two CNAME's to ELBs are what needs to be changed in DNS (and then the step of cutting off DNS to the old stack for yahoo.login.persona.org (1001) stack).
(Reporter)

Comment 2

4 years ago
Okay, after a slight delay while dynect fixed some sort of DNS zone problem on their backend, the 1015 stacks started getting traffic at about 'Tue Oct 15 16:38:40 PDT 2013', and requests to 1001 were disabled @ 'Tue Oct 15 16:51:18 PDT 2013'.

Closing as fixed.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
(Reporter)

Updated

4 years ago
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.