Closed
Bug 1196964
Opened 10 years ago
Closed 10 years ago
[Air Mozilla] optisorl not installed in dev
Categories
(Infrastructure & Operations :: IT-Managed Tools, task)
Infrastructure & Operations
IT-Managed Tools
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: peterbe, Assigned: ericz)
Details
(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/1597] )
optisorl is a new package that I've added to the requirements.txt
It gets installed fine
E.g. http://genericadm.private.phx1.mozilla.com/chief/air.dev/logs/master.1440107641 (you have to find-in-page to see that `optisorl` does get installed)
However, upon runtime it seems this package can't be imported. It's important sort of "on the fly" because it's "lazy" meaning it doesn't get imported until it's needed.
To simulate it, start a django shell and you should be able to do this::
(airmozilla):~/dev/MOZILLA/AIRMOZILLA/airmozilla (master $)$ s
>>> from sorl.thumbnail.helpers import get_module_class
>>> from django.conf import settings
>>> get_module_class(settings.THUMBNAIL_BACKEND)()
<optisorl.backend.OptimizingThumbnailBackend object at 0x107497450>
Reporter | ||
Comment 1•10 years ago
|
||
This is the first package added to requirements.txt since we move air-dev.allizom.org to python 2.7
Reporter | ||
Comment 2•10 years ago
|
||
Shyam,
Can I get some help here. Eric is taking today off he told me on IRC.
The concern here is that we're due to upgrade Air Mozilla to the Python 2.7 cluster next week and between Errormill being down and dev now not working I'm losing confidence and might have to postpone the CAB.
I can't explain what's going on here but I suspect that, new additions to the virtualenv don't get included when moved into the webheads. I even tried doing another dev chief deployment to see if it needs to run at least more than once to take effect or something but it didn't help.
Flags: needinfo?(smani)
Assignee | ||
Comment 3•10 years ago
|
||
At least part of the issue would appear to be update.py deleting the existing python executable and recreating it using virtualenv which installs python 2.6 instead of virtualenv-2.7 which would recreate the correct python 2.7 executable. Switching to virtualenv-2.7 in update.py should keep us on the right version of python.
Assignee | ||
Updated•10 years ago
|
Flags: needinfo?(smani)
Assignee | ||
Updated•10 years ago
|
Assignee: server-ops-webops → eziegenhorn
Assignee | ||
Comment 4•10 years ago
|
||
Issue is confirmed fixed now.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•