Closed
Bug 1390197
Opened 7 years ago
Closed 7 years ago
please deploy balrog 2.37 to prod
Categories
(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)
Cloud Services
Operations: Deployment Requests - DEPRECATED
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: bhearsum, Assigned: relud)
References
Details
Balrog version 2.37 is ready to be pushed to prod. Please deploy the new Docker images (master-e99b26ba54acb807ed699a63fa681447187cbcb8) for admin, public, and the agent.
We'd like the production push for this to happen as early as possible on Monday, August 14th.
There is a migration that removes a column from some tables in this push. We simulated it in stage on Friday, and determined that this is the correct order of operations:
- Deploy web. We can do the normal ~1h canary here still, but we can't proceed further until we are 100% on the new web cluster.
- Deploy admin/agent; run migration. Verify that admin and web still work after the migration.
Assignee | ||
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Reporter | ||
Updated•7 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•