Timezone support is unclear
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
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.
from src/maas/
# 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:/
[2] https:/
Changed in maas: | |
milestone: | none → 1.9.0 |
Changed in maas: | |
status: | New → Triaged |
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.