798162 - Enable BigTent in stage for yahoo

Status: RESOLVED FIXED

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

Description

[Austin King [:ozten]]

Please add this to one of the *stage only* .json config files:


    "proxy_idps": {
        "yahoo.com": "yahoo.login.anosrep.org"
    },

Comment 1

[Gene Wood [:gene]]

This is updated in sysadmins r49173 and deployed to stage

Comment 2

[ozten]

Yahoo BigTent is disabled in stage now.

Can we re-enable it? This is a config only change on Persona stage servers.

Comment 3

[Gene Wood [:gene]]

Sure, what is the config change?

Comment 4

[ozten]

Please add this to one of the *stage only* .json config files:


    "proxy_idps": {
        "yahoo.com": "yahoo.login.anosrep.org"
    },

Comment 5

[Gene Wood [:gene]]

Hmm.. I'm confused. I made that change with you in breckenridge and deployed it to stage back on 10/4. That's how we got bigtent working in staging (See Comment 1). Give me more details on what you're looking for. Here's the diff of that commit I mentioned above :


Thu Oct 11 10:38:46 gene@ruth:~/Documents/coderepo/svn.mozilla.org/sysadmins$ svn diff -r 49173:49172
Index: puppet/weave/modules/browserid/templates/production.json.stage
===================================================================
--- puppet/weave/modules/browserid/templates/production.json.stage	(revision 49173)
+++ puppet/weave/modules/browserid/templates/production.json.stage	(revision 49172)
@@ -38,9 +38,5 @@
   "verifier_url": "https://browserid.org",
   "keysigner_url": "http://keysign.idkeysign.scl2.stage.svc.mozilla.com",
   "dbwriter_url": "http://dbwriter.idsecweb.scl2.stage.svc.mozilla.com",
-  "browserid_url": "http://127.0.0.1:62700",
-
-  "proxy_idps": {
-    "yahoo.com": "yahoo.login.anosrep.org"
-  }
+  "browserid_url": "http://127.0.0.1:62700"
 }

Comment 6

[ozten]

Okay, request https://login.anosrep.org/wsapi/address_info?email=eozten%40yahoo.com 5 times. It flops between saying yahoo.com is bigtent enabled and saying the address is a secondary.

I don't think this config is on all the stage boxes.

Comment 7

[Gene Wood [:gene]]

bingo. Indeed the config had been updated back on 10/4 on all webheads. web3.idweb however had not had it's process manually restarted (which is current required). I've restarted it now and confirmed it's process start date.

I will need to get a service notification added to our puppet script so when a config changes, the service is restarted.

Comment 8

[ozten]

Yay, stage is working again. Thanks!