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

Please re-deploy Tokenserver 1.2.9 to Production w/ updated AMI

VERIFIED FIXED

Status

Cloud Services
Operations: Deployment Requests
VERIFIED FIXED
3 years ago
3 years ago

People

(Reporter: mostlygeek, Assigned: mostlygeek)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [qa+])

(Assignee)

Description

3 years ago
To address 500 errors (due to high load) in #1038770

Re-deploy tokenserver to prod w/ the latest AMIs which include the no ephemeral0 storage issue.
(Assignee)

Updated

3 years ago
Depends on: 1039803
:mostlygeek I am a bit confused by this.
What happened in bug 1038770 (which I thought was a good deploy) to cause another deploy to Prod?
Status: NEW → ASSIGNED
(Assignee)

Comment 2

3 years ago
for the record all things explained in bug 1039803
:mostlygeek do you have a schedule for this deploy to Production?
(Assignee)

Comment 4

3 years ago
Deployed.
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
Well, if something went wrong over the weekend, :mostlygeek would have said so by now...
:-)
Status: RESOLVED → VERIFIED
FYI - may quick verification testing of TS was successful.
You need to log in before you can comment on or make changes to this bug.