CL 288396 is causing suite scheduler to fail to start due to error:
$ /usr/local/autotest/site_utils/suite_scheduler/suite_scheduler.py -b -d /usr/local/autotest/logs -f /usr/local/autotest/suite_scheduler.ini
Traceback (most recent call last):
File "/usr/local/autotest/site_utils/suite_scheduler/suite_scheduler.py", line 48, in <module>
from autotest_lib.site_utils import server_manager_utils
File "/usr/local/autotest/site_utils/server_manager_utils.py", line 19, in <module>
from autotest_lib.frontend.server import models as server_models
File "/usr/local/autotest/frontend/server/models.py", line 8, in <module>
from django.db import models as dbmodels
File "/usr/local/autotest/site-packages/django/db/__init__.py", line 11, in <module>
if settings.DATABASES and DEFAULT_DB_ALIAS not in settings.DATABASES:
File "/usr/local/autotest/site-packages/django/conf/__init__.py", line 53, in __getattr__
self._setup(name)
File "/usr/local/autotest/site-packages/django/conf/__init__.py", line 46, in _setup
% (desc, ENVIRONMENT_VARIABLE))
django.core.exceptions.ImproperlyConfigured: Requested setting DATABASES, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings.
Change-Id: I41232fa2bb8380f1fddcf664f55a2285d196e6e8
Reviewed-on: https://chromium-review.googlesource.com/290271
Reviewed-by: Dan Shi <dshi@chromium.org>
Commit-Queue: Dan Shi <dshi@chromium.org>
Tested-by: Dan Shi <dshi@chromium.org>
5 files changed