Closed Bug 826277 Opened 12 years ago Closed 11 years ago

Fix support-dev deploys

Categories

(support.mozilla.org :: General, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED FIXED
2013Q1

People

(Reporter: rrosario, Assigned: mythmon)

References

Details

(Whiteboard: u=dev c=general p=2 s=2013.1)

Since upgrading to django 1.4, deploys to -dev have been failing to complete. The latest log can be seen at: http://support-dev.allizom.org/media/revision_info.txt

[2013-01-02 04:27:16] [localhost] running: cd /data/support-dev/src/support-dev.allizom.org/kitsune && python2.6 ./vendor/src/schematic/schematic -v migrations/
[2013-01-02 04:27:17] [localhost] failed: cd /data/support-dev/src/support-dev.allizom.org/kitsune && python2.6 ./vendor/src/schematic/schematic -v migrations/ (0.323s)
[localhost] out: Error: Couldn't find value for 'db' in settings.py
[2013-01-02 04:27:17] Running update
[2013-01-02 04:27:17] Running update_assets
[2013-01-02 04:27:17] [localhost] running: cd /data/support-dev/src/support-dev.allizom.org/kitsune && python2.6 manage.py collectstatic --noinput
[2013-01-02 04:27:17] [localhost] failed: cd /data/support-dev/src/support-dev.allizom.org/kitsune && python2.6 manage.py collectstatic --noinput (0.249s)
[localhost] err: Traceback (most recent call last):
[localhost] err: File "manage.py", line 48, in <module>
[localhost] err: import session_csrf
[localhost] err: File "/data/support-dev/src/support-dev.allizom.org/kitsune/vendor/src/django-session-csrf/session_csrf/__init__.py", line 5, in <module>
[localhost] err: from django.core.cache import cache
[localhost] err: File "/data/support-dev/src/support-dev.allizom.org/kitsune/vendor/src/django/django/core/cache/__init__.py", line 76, in <module>
[localhost] err: if not settings.CACHES:
[localhost] err: File "/data/support-dev/src/support-dev.allizom.org/kitsune/vendor/src/django/django/utils/functional.py", line 184, in inner
[localhost] err: self._setup()
[localhost] err: File "/data/support-dev/src/support-dev.allizom.org/kitsune/vendor/src/django/django/conf/__init__.py", line 42, in _setup
[localhost] err: self._wrapped = Settings(settings_module)
[localhost] err: File "/data/support-dev/src/support-dev.allizom.org/kitsune/vendor/src/django/django/conf/__init__.py", line 95, in __init__
[localhost] err: raise ImportError("Could not import settings '%s' (Is it on sys.path?): %s" % (self.SETTINGS_MODULE, e))
[localhost] err: ImportError: Could not import settings 'freddo.settings' (Is it on sys.path?): No module named freddo.settings


It looks like freddo isn't playing nicely with our manage.py or the path is somehow screwed up or ???

Hopefully, the fix is as simple as setting the DJANGO_SETTINGS_MODULE environment variable in manage.py. Like:
https://docs.djangoproject.com/en/dev/releases/1.4/#updated-default-project-layout-and-manage-py

I think AMO/Zamboni is on django 1.4, so we could check with them for pointers as well.
Putting in the current sprint in case anybody gets a chance to play take a look, otherwise it will go into the next one during planning.
Whiteboard: u=dev c=general p= s=2012.24
Moving to next sprint.
Whiteboard: u=dev c=general p= s=2012.24 → u=dev c=general p= s=2013.1
Whiteboard: u=dev c=general p= s=2013.1 → u=dev c=general p=2 s=2013.1
Assignee: nobody → mcooper
Depends on: 828033
Blocks: 828136
No longer blocks: 828136
Depends on: 828735
PR: https://github.com/mozilla/kitsune/pull/1038.

This has landed in master in https://github.com/mythmon/kitsune/commit/8aa969f18f06da5e6fde4538948504429d3d5fbf.

Dev is working again, and we tested pushing this to stage, to make sure it didn't break things. No need to push this to prod, so closing this out.

NB: Bug 88735 still needs done before this is truly fixed, but there is no more work that needs done here.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.