Timezone support is unclear

Bug #1464320 reported by Gavin Panella on 2015-06-11
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Medium
Unassigned

Bug Description

In MAAS's Django configuration, USE_TZ is False and TIME_ZONE is None.

Django's docs on timezone support [1] imply that this is fine,
presumably as long as we stick to datetime.datetime.now(). A comment
from src/maas/settings.py supports this:

# On Unix systems, a value of None will cause Django to use the same
# timezone as the operating system.

So: using datetime.now() appears it will DTRT, if a little bit by
accident. However, datetime.utcnow() is used in a few places, and I
imagine that won't work for folk running their servers with local
timezones that don't match UTC.

This was first discussed in the merge proposal for the VLAN & Fabric
models [2].

[1] https://docs.djangoproject.com/en/1.6/topics/i18n/timezones/
[2] https://code.launchpad.net/~rvb/maas/add-vlan-fabric/+merge/261693

Changed in maas:
milestone: none → 1.9.0
Raphaël Badin (rvb) wrote :

This needs further investigation before we can properly triage the severity of this but marking it 'Medium' for now since it hasn't caused any real issue in practice so far.

Changed in maas:
importance: Undecided → Medium
Gavin Panella (allenap) on 2015-09-02
Changed in maas:
status: New → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers