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)
Tree Management
Treeherder
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: emorley, Assigned: camd)
References
Details
Attachments
(1 file)
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.
Comment 2•10 years ago
|
||
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)
Comment 3•10 years ago
|
||
looks like the newrelic plugin agent is the only *rpm* that depends on importlib
Comment 4•10 years ago
|
||
manual yak shaving required, but it can be done. will work on adding it to staging this afternoon.
Comment 5•10 years ago
|
||
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 | ||
Updated•10 years ago
|
Assignee: nobody → cdawson
Status: NEW → ASSIGNED
Assignee | ||
Comment 7•10 years ago
|
||
Attachment #8556214 -
Flags: review?(mdoglio)
Reporter | ||
Comment 8•10 years ago
|
||
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 9•10 years ago
|
||
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+
Comment 10•10 years ago
|
||
python27 installed on prod
Comment 11•10 years ago
|
||
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.
Comment 12•10 years ago
|
||
The are already installed; see treeherderadm:/data/treeherder/src/treeherder.mozilla.org/*requirements.txt
Comment 13•10 years ago
|
||
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?
Comment 14•10 years ago
|
||
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.
Reporter | ||
Comment 15•10 years ago
|
||
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? :-)
Comment 16•10 years ago
|
||
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.
Assignee | ||
Comment 17•10 years ago
|
||
(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.
Reporter | ||
Comment 18•10 years ago
|
||
(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 :-)
Comment 19•10 years ago
|
||
Commits pushed to master at https://github.com/mozilla/treeherder-service
https://github.com/mozilla/treeherder-service/commit/5cbe0fd843dd6853eddad741f757e7feeb1eecda
Bug 1119479 - Remove python 2.6 testing
https://github.com/mozilla/treeherder-service/commit/698fd0551907d7c8c29514d9a897718e06b23e28
Bug 1119479 - Upgrade to Django 1.7
https://github.com/mozilla/treeherder-service/commit/0c45e01bf90ee7b631c0bd620350d3cf7dd35d97
Bug 1119479 - Remove South
https://github.com/mozilla/treeherder-service/commit/eabe3a47de94d5debb009bfd5973b4779e1bbbb0
Bug 1119479 - Fix update script and puppet manifest
Assignee | ||
Updated•10 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 20•10 years ago
|
||
The Python 2.6->2.7 update appears to have sped up quite a few tasks. The gap in these timelines is when python was updated (the timeline for that differs from node to node, since the change was only picked up when the tasks were restarted aiui):
https://rpm.newrelic.com/accounts/677903/applications/4180461/transactions?tw[end]=1423775699&tw[start]=1423689299#id=606282991&tab-transaction-680024271=app_server_historical_performance
https://rpm.newrelic.com/accounts/677903/applications/4180461/transactions?tw[end]=1423776084&tw[start]=1423516884#id=570791502&tab-transaction-680024271=app_server_historical_performance
https://rpm.newrelic.com/accounts/677903/applications/4180461/transactions?tw[end]=1423776084&tw[start]=1423516884#id=570791471&tab-transaction-680024271=app_server_historical_performance
Reporter | ||
Updated•10 years ago
|
Reporter | ||
Updated•10 years ago
|
Summary: Update to something newer than Django 1.5, since it's unsupported → Update to Django 1.7, since 1.5 is unsupported
You need to log in
before you can comment on or make changes to this bug.
Description
•