UnknownTimeZoneError on various pages

[Henning Eggers]

I don't think this should cause a page to oops ...

https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1264B288
https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1264C1002
https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1264C901

69 instances on that day.

[Stuart Bishop (stub)]

Edge is now running with pytz 2009i. It allows users to set their timezones to values not understood by the production systems (production seems to be using the system installed pytz 2008c linked to the Ubuntu zoneinfo files).

Installing a more modern pytz will work around the issue for now.

We need to consider how we handle package upgrades in the future - buildout now makes it easier to upgrade our dependencies, and every time we do so we risk similar issues occurring due to the version skew between production and edge.

[Данило Шеган (danilo)]

Am I understanding this right: this will be fixed as soon as we roll out 2.2.6? If so, we need to roll out pytz 2009i on production servers sooner than that.

[Stuart Bishop (stub)]

Reverting edge and cleaning the production data is impractical.

I'll suggest downloading latest pytz (http://pypi.python.org/packages/source/p/pytz/pytz-2009j.tar.bz2) and installing on all the appservers:

mkdir -p /srv/staging.launchpad.net/lib/python
export PYTHONPATH=/srv/staging.launchpad.net/lib/python
python2.4 setup.py install --home=/srv/staging.launchpad.net

Then startup the appservers so they start with PYTHONPATH set to /srv/staging.launchpad.net/lib/python.

[Stuart Bishop (stub)]

Tom - can you chase this through to completion, or reassign if people in your timezone think a code fix and cherry pick a better option?

[Tom Haddon (mthaddon)]

pytz2009j has been installed on the lpnet app servers - 2.2.6 rollout should include this fix properly.