Closed Bug 1119479 Opened 10 years ago Closed 10 years ago

Update to Django 1.7, since 1.5 is unsupported

Categories

(Tree Management :: Treeherder, defect, P2)

Product:
Tree Management
Component:
Treeherder
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: emorley, Assigned: camd)

References

Details

Attachments

(1 file)

pr 343
54 bytes, text/x-github-pull-request
mdoglio
: review+
Details | Review
From a recent email: > In March or April of 2015, Django will release Django 1.8. When that happens Django 1.6 will no longer be supported. Further, since 1.8 is the next Long Term Support release, Django 1.4 support will end 6 months after the 1.8 release. > > https://code.djangoproject.com/wiki/Version1.8Roadmap > > https://docs.djangoproject.com/en/dev/releases/1.8/ > > > This has the following ramifications: > > 1. If you're using Django 1.4, you need to start thinking about upgrading. Write up bugs now. Might make sense to upgrade directly to 1.8. Assume you're going to have to do a lot of work. > > 2. If you're using Django 1.5, you're using an unsupported release. Write up bugs today. Upgrade to 1.6 ASAP. > > 3. If you're using Django 1.6, you should upgrade to Django 1.7 soon. Write up bugs today. Upgrade this quarter. > > 4. If you're using Python 2.6, you need to upgrade to Python 2.7 ASAP. Bug IT/webops until they have you on the schedule.
:fubar how much effort is to move to py27?
Flags: needinfo?(klibby)
I thought it would be fairly easy, but right off the bat: Error: python-importlib conflicts with python27-2.7.8-1.ius.el6.x86_64 I'm not sure *why* unless they think they both own /usr/share/doc.. (all package managers)-- :-P I'll see if I can get python27 on staging without breaking things.
Flags: needinfo?(klibby)
looks like the newrelic plugin agent is the only *rpm* that depends on importlib
manual yak shaving required, but it can be done. will work on adding it to staging this afternoon.
side-along python27 installed on all staging nodes (system python is still 2.6). fwiw, takes about an hour to install. pip is just sketchy enough that automating it is likely to cause problems. :-P if nothing catches fire, I can do production early next week.
Assignee: nobody → cdawson
Status: NEW → ASSIGNED
Attached file pr 343 —
Attachment #8556214 - Flags: review?(mdoglio)
Bug 1125585 also included https://github.com/jeads/datasource/pull/17 which supposedly fixed OperationalError 2006's when using datasource with Django 1.6, if that helps (don't know if you'd seen any of these on dev).
Comment on attachment 8556214 [details] [review] pr 343 Thanks for working on this :-) Can we please wait to have py27 on production before landing this on master? It would be annoying to not being able to push any other fix to prod because of it.
Attachment #8556214 - Flags: review?(mdoglio) → review+
python27 installed on prod
So I guess the next step is to install all the libraries in requirements/compiled.txt in the new environment on both stage and prod.
The are already installed; see treeherderadm:/data/treeherder/src/treeherder.mozilla.org/*requirements.txt
On treeherder1.webapp I'm getting this Python 2.7.8 (default, Jul 3 2014, 17:42:16) [GCC 4.4.7 20120313 (Red Hat 4.4.7-4)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import django Traceback (most recent call last): File "<stdin>", line 1, in <module> ImportError: No module named django Am I doing something dumb?
oh, derp. need to install them for py27. man, I can' even blame jetlag for that one... will add it to puppet to install after lunch.
Cam, I was going to update dev a bit (eg latest master, recompile log parsers, sync oauth keys to worker etc - since getting errors like https://rpm.newrelic.com/accounts/677903/applications/6030200/traced_errors/3067757528) but don't want to interrupt your testing. When you're done with dev & ready to put back to master, I don't suppose you could do those - or let me know and I will? :-)
pip and DC proxies made this vastly more difficult, but all of the python modules are installed on staging and prod. please shout if you see anything weird (particularly on treeherder-etl1.stage) or missing.
(In reply to Ed Morley [:edmorley] from comment #15) > Cam, I was going to update dev a bit (eg latest master, recompile log > parsers, sync oauth keys to worker etc - since getting errors like > https://rpm.newrelic.com/accounts/677903/applications/6030200/traced_errors/ > 3067757528) but don't want to interrupt your testing. When you're done with > dev & ready to put back to master, I don't suppose you could do those - or > let me know and I will? :-) Hi Ed-- I did all that on dev now. It is still on the django-1.7 branch. But that branch was rebased against latest master and dev updated to it.
(In reply to Cameron Dawson [:camd] from comment #17) > Hi Ed-- I did all that on dev now. It is still on the django-1.7 branch. > But that branch was rebased against latest master and dev updated to it. That's great - thank you :-)
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Depends on: 1133138
Depends on: 1133273
Depends on: 1133870
Depends on: 1133910
No longer depends on: 1133870
Summary: Update to something newer than Django 1.5, since it's unsupported → Update to Django 1.7, since 1.5 is unsupported
Depends on: 1134140
No longer depends on: 1134140
Depends on: 1136380
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: