[6.1/Trunk] server timezone config is silently ignored
Bug #970538 reported by
Carlos Vásquez (ClearCorp)
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Odoo Server (MOVED TO GITHUB) |
Confirmed
|
Low
|
OpenERP's Framework R&D |
Bug Description
The server timezone is always set to UTC as of v6.1 as a design choice. The corresponding timezone config value is however still accepted but silently ignored, so the admin is never notified of this fact. A warning message should be printed at least.
=== Original description ===
The server timezone is always set to UTC. The timezone config value is not used.
Related branches
lp:~cv.clearcorp/openobject-server/lp-970538-timezone
- ClearCorp development team: Pending requested
-
Diff: 13 lines (+3/-0)1 file modifiedopenerp-server (+3/-0)
On hold
for merging
into
lp:openobject-server/6.1
- Olivier Dony (Odoo): Disapprove (tech analysis)
-
Diff: 13 lines (+3/-0)1 file modifiedopenerp-server (+3/-0)
Changed in openobject-server: | |
assignee: | nobody → OpenERP's Framework R&D (openerp-dev-framework) |
importance: | Undecided → Low |
status: | New → Confirmed |
summary: |
- [6.1] server timezone config is ignored, UTC always + [6.1/Trunk] server timezone config is ignored, UTC always |
summary: |
- [6.1/Trunk] server timezone config is ignored, UTC always + [6.1/Trunk] server timezone config is ignored without warning, UTC is + always used as of 6.1 |
description: | updated |
summary: |
- [6.1/Trunk] server timezone config is ignored without warning, UTC is - always used as of 6.1 + [6.1/Trunk] server timezone config is silently ignored |
To post a comment you must log in.
Hi,
It is a design choice in OpenERP 6.1 to forcefully set the server timezone to UTC and ignore the previous --timezone configuration parameter. There are many good reasons for this, and you may find some further explanations about them in some related bug reports: bug 918257 (especially comment #4) and further technical discussions in bug 925361.
I understand that this may look like a bug because the --timezone option was not removed and does not report a warning when you try to use it. So I suggest we change the description of this bug to explain that this is confusing and needs to be changed.
Thanks!