Cluster controllers don't have their own amqp queues yet
Bug #1055523 reported by
Jeroen T. Vermeulen
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Critical
|
Jeroen T. Vermeulen | ||
Bug Description
At the moment, celeryd in the cluster controller is set up to listen on the default rabbit queue called "celery." To get the routing right, a cluster controller should listen to its own queue named after its uuid (plus the 'common' queue used for broadcast messages). The queue will be autocreated by celery.
Related branches
lp:~jtv/maas/bug-1055523-cluster-uuid
- Raphaël Badin (community): Approve
-
Diff: 144 lines (+19/-23)4 files modifiedcontrib/maas_local_celeryconfig.py (+4/-1)
etc/celeryconfig.py (+4/-0)
src/provisioningserver/start_cluster_controller.py (+5/-18)
src/provisioningserver/tests/test_start_cluster_controller.py (+6/-4)
lp:~jtv/maas/pkg-1055523-cluster-uuid
- Raphaël Badin (community): Approve
-
Diff: 16 lines (+6/-0)1 file modifieddebian/maas.postinst (+6/-0)
| description: | updated |
| Changed in maas: | |
| importance: | High → Critical |
| description: | updated |
| Changed in maas: | |
| assignee: | nobody → Jeroen T. Vermeulen (jtv) |
| status: | Triaged → In Progress |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
