celeryconfig_cluster.py imports utility method from maas (import_settings)

Bug #1065055 reported by Raphaël Badin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Critical
Jeroen T. Vermeulen

Bug Description

When the cluster controller is installed on separate machine (i.e. not next to the region controller), the import blows up.

Related branches

Raphaël Badin (rvb)
description: updated
Changed in maas:
milestone: none → 12.10
Revision history for this message
John A Meinel (jameinel) wrote :

Is this a packaging issue (python-maas should be installed on the cluster controllers), or just a 'we should copy and paste the code so it is available without importing' issue?

Revision history for this message
Julian Edwards (julian-edwards) wrote :

Fixing in packaging for now, it's a one-liner.

Changed in maas (Ubuntu):
status: New → In Progress
assignee: nobody → Julian Edwards (julian-edwards)
no longer affects: maas
Revision history for this message
Raphaël Badin (rvb) wrote :

Can't be done in the packaging because the 'maas' package (which contains Django settings) is not on the path (standard Django application packaging policy). For now, let's copy over the 2 methods in the celeryconfig_cluster.py and file a tech-debt bug.

Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

Stealing this bug from Julian since he's packing, not packaging right now. :)

Changed in maas (Ubuntu):
assignee: Julian Edwards (julian-edwards) → Jeroen T. Vermeulen (jtv)
Raphaël Badin (rvb)
affects: maas (Ubuntu) → maas
Changed in maas:
importance: Undecided → Critical
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.