django.core.exceptions.AppRegistryNotReady: Models aren't loaded yet. when starting MAAS with Django 1.7

Bug #1431741 reported by Raphaël Badin on 2015-03-13
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Critical
Raphaël Badin

Bug Description

Full stacktrace: http://paste.ubuntu.com/10589786/

This happens because the Twisted service try to use the ORM before the models are loaded (see https://docs.djangoproject.com/en/1.7/ref/applications/#troubleshooting). The solution should be simple: force the models to be loaded *before* any Twisted service is started (`import django; django.setup()`).

Related branches

Raphaël Badin (rvb) on 2015-03-13
Changed in maas:
assignee: nobody → Raphaël Badin (rvb)
status: Triaged → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers