Closed
Bug 1361728
Opened 8 years ago
Closed 8 years ago
please deploy balrog 2.27 to prod
Categories
(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)
Cloud Services
Operations: Deployment Requests - DEPRECATED
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: miles)
References
Details
Balrog version 2.27 is ready to be pushed to stage. Please deploy the new Docker images (master-19b506d80c9070610956ae11bd2f1c0bc310f319) for admin, public, and the agent.
We'd like the production push for this to happen sometime between 11am and 1pm pacific on Wednesday, May 3.
Reporter | ||
Updated•8 years ago
|
Reporter | ||
Updated•8 years ago
|
Summary: please deploy balrog 2.27 to stage/prod → please deploy balrog 2.27 to prod
Reporter | ||
Comment 1•8 years ago
|
||
This was completed yesterday with some hiccups:
1) The web cluster was serving all 500s for awhile, because I forgot there was a schema change (which should've been done after the entire new web cluster was rolled out).
2) We're seeing an elevated rate of 500s due to https://sentry.prod.mozaws.net/operations/prod-public/issues/595860/. I'm going to be backing out the patch that's at fault and we'll deploy that in a new bug.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•