Closed
Bug 1290315
Opened 8 years ago
Closed 8 years ago
Please deploy tokenserver 1.2.23
Categories
(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)
Cloud Services
Operations: Deployment Requests - DEPRECATED
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: rfkelly, Assigned: mostlygeek)
References
Details
This version includes support for returning the hashed FxA uid to the client, to be included in metrics pings, per Bug 1288445 Tagged at: https://github.com/mozilla-services/tokenserver/releases/tag/1.2.23
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → bwong
Assignee | ||
Comment 1•8 years ago
|
||
This has been deployed to stage. :rfkelly, does this need to be QA'd before rolling out to prod?
Assignee | ||
Updated•8 years ago
|
Flags: needinfo?(rfkelly)
Reporter | ||
Comment 2•8 years ago
|
||
Yes, a basic sanity-check is probably a good idea :-) ni? Karl for a loadtest run, and ni? :markh to confirm whether the expected new field is being returned in the tokenserver response from stage in the correct fashion
Flags: needinfo?(rfkelly)
Flags: needinfo?(markh)
Flags: needinfo?(kthiessen)
Comment 3•8 years ago
|
||
I will run load tests against this tomorrow or Thursday and report back results.
Flags: needinfo?(kthiessen)
Comment 4•8 years ago
|
||
(In reply to Ryan Kelly [:rfkelly] from comment #2) > ni? Karl for a loadtest run, and ni? :markh to confirm whether the expected > new field is being returned in the tokenserver response from stage in the > correct fashion Thom is working on atomic writes (which also requires use of stage) and is also assigned the bug for sending this hash in the ping, so I'll punting the needinfo to him :)
Flags: needinfo?(markh) → needinfo?(tchiovoloni)
Comment 6•8 years ago
|
||
Ack, sorry about this, I was looking at the fxa_uid field yesterday (I was still recovering from being sick -- sorry!) Anyway, as far as I can tell, the hashed_fxa_uid field is *not* on stage... Unless I'm configured wrong, which is totally possible (The tokenserver uri is https://token.stage.mozaws.net/1.0/sync/1.5, and the server claims to be https://sync-1-us-east-1.stage.mozaws.net). Ping me on irc if you think this is the case.
Flags: needinfo?(bwong)
Assignee | ||
Comment 7•8 years ago
|
||
Version (1.2.23) of tokenserver is on stage. https://token.stage.mozaws.net is also the correct endpoint.
Flags: needinfo?(bwong)
Comment 8•8 years ago
|
||
I just tested against staging and when requesting a token from https://token.stage.mozaws.net/1.0/sync/1.5, the response included |hashed_fxa_uid:"baaa901a7890c6d5fc63656586fde509"|, so ISTM that this is working correctly.
Comment 9•8 years ago
|
||
Load tests return unsurprising values, according to both bobm and myself. This looks to be good to go to prod.
QA Contact: kthiessen
Updated•8 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 10•8 years ago
|
||
Deployed to production.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•