Closed Bug 1260789 Opened 8 years ago Closed 8 years ago

[remo] Upgrade celery in all remo deployments

Categories

(Infrastructure & Operations Graveyard :: WebOps: Engagement, task)

Product:
Infrastructure & Operations Graveyard
Component:
WebOps: Engagement
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: nemo-yiannis, Assigned: ericz)

References

Details

(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/2779] ) 

We are upgrading to the latest LTS version of django (1.8.x) in reps.mozilla.org. This is a hard dependency since our current version (1.7.x) is EOLed, so we are not receiving the last security updates.

In order to upgrade to latest Django LTS we need to also upgrade celery (v3.x).
How can we coordinate in order to upgrade our cluster's celery version?
Here is the bug tracking a similar effort already done for Mozillians.org
https://bugzilla.mozilla.org/show_bug.cgi?id=1252078
Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/2779]
Assignee: server-ops-webops → eziegenhorn
As per that bug you referenced, you should be able to upgrade celery by specifying a version in your requirements and redeploying.  I'd suggest trying it in dev and we'll work our way on up, scheduling the prod change through CAB.
Timeout, please re-open when you're ready to go.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
This has been addressed in order to tackle bug 1173705. Marking this one as resolved.
Resolution: INCOMPLETE → FIXED
Blocks: 1173705
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.