Bug 1238460
| Summary: | RHEL Images for overcloud use EDT as timezone | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Graeme Gillies <ggillies> | |
| Component: | openstack-tripleo-heat-templates | Assignee: | James Slagle <jslagle> | |
| Status: | CLOSED ERRATA | QA Contact: | Omri Hochman <ohochman> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | urgent | |||
| Version: | 7.0 (Kilo) | CC: | cchen, cylopez, dhill, djuran, dmacpher, hbrock, jdonohue, jslagle, mburns, nauvray, racedoro, rhel-osp-director-maint, sasha, sputhenp, ushkalim | |
| Target Milestone: | y3 | Keywords: | Triaged, ZStream | |
| Target Release: | 7.0 (Kilo) | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | openstack-tripleo-heat-templates-0.8.6-113.el7ost | Doc Type: | Bug Fix | |
| Doc Text: |
Previous Overcloud images used EDT for the timezone, which caused problems for users outside of the EDT timezone. This fix adds a customizable 'TimeZone' parameter to the Heat template collection. Users can set the 'TimeZone' parameter to their own timezone. If blank, it defaults to UTC.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1299081 1309818 (view as bug list) | Environment: | ||
| Last Closed: | 2016-02-18 16:46:41 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1191185, 1243520, 1299081, 1309818, 1311366 | |||
|
Description
Graeme Gillies
2015-07-01 23:56:41 UTC
Hi guys, Would it be possible to add a configuration parameter for this so any timezone could be used ? Some companies requires the timezone to be UTC, some other might require to have their local timezone configured. Thank you very much, David Hill *** Bug 1274620 has been marked as a duplicate of this bug. *** From: openstack-tripleo-heat-templates-0.8.6-120.el7ost.noarch
[root@overcloud-controller-1 ~]# timedatectl
Local time: Tue 2016-02-16 16:42:07 UTC
Universal time: Tue 2016-02-16 16:42:07 UTC
RTC time: Tue 2016-02-16 16:42:06
Time zone: UTC (UTC, +0000)
NTP enabled: yes
NTP synchronized: yes
RTC in local TZ: no
DST active: n/a
Will try to modify the default value and will update with results.
[root@overcloud-controller-0 ~]# date
Wed Feb 17 10:12:54 UTC 2016
[root@overcloud-controller-0 ~]# timedatectl
Local time: Wed 2016-02-17 10:13:03 UTC
Universal time: Wed 2016-02-17 10:13:03 UTC
RTC time: Wed 2016-02-17 10:13:03
Time zone: IST (UTC, +0000)
NTP enabled: yes
NTP synchronized: yes
RTC in local TZ: no
DST active: n/a
[root@overcloud-controller-0 ~]# ls -ltr /etc/localtime
lrwxrwxrwx. 1 root root 23 Feb 16 20:40 /etc/localtime -> /usr/share/zoneinfo/IST
[root@overcloud-controller-0 ~]# ls -ltr /usr/share/zoneinfo/IST
ls: cannot access /usr/share/zoneinfo/IST: No such file or directory
It seems to be failing to configuring the correct timezone...
seems like I'm getting EST time-zone on the OC
[root@overcloud-controller-0 ~]# date
Wed Feb 17 15:18:38 EST 2016
[root@overcloud-controller-0 ~]# timedatectl
Local time: Wed 2016-02-17 15:18:46 EST
Universal time: Wed 2016-02-17 20:18:46 UTC
RTC time: Wed 2016-02-17 20:18:45
Timezone: America/New_York (EST, -0500)
NTP enabled: yes
NTP synchronized: yes
RTC in local TZ: no
DST active: no
Last DST change: DST ended at
Sun 2015-11-01 01:59:59 EDT
Sun 2015-11-01 01:00:00 EST
Next DST change: DST begins (the clock jumps one hour forward) at
Sun 2016-03-13 01:59:59 EST
Sun 2016-03-13 03:00:00 EDT
[root@overcloud-controller-0 ~]# ls -ltr /etc/localtime
lrwxrwxrwx. 1 root root 38 Oct 7 10:36 /etc/localtime -> ../usr/share/zoneinfo/America/New_York
[root@overcloud-controller-0 ~]# ls -ltr /usr/share/zoneinfo/America/New_York
-rw-r--r--. 3 root root 3519 Aug 11 2015 /usr/share/zoneinfo/America/New_York
Environment:
openstack-tripleo-heat-templates-0.8.6-121.el7ost.noarch
I'm getting UTC:
[root@overcloud-controller-0 ~]# date
Thu Feb 18 03:24:28 UTC 2016
[root@overcloud-controller-0 ~]# timedatectl
Local time: Thu 2016-02-18 03:24:31 UTC
Universal time: Thu 2016-02-18 03:24:31 UTC
RTC time: Thu 2016-02-18 03:24:31
Time zone: UTC (UTC, +0000)
NTP enabled: yes
NTP synchronized: yes
RTC in local TZ: no
DST active: n/a
Depoyed with:
TimeZone: Asia/Tel_Aviv
And got:
[root@overcloud-controller-2 ~]# date
Thu Feb 18 06:02:35 IST 2016
[root@overcloud-controller-2 ~]# timedatectl
Local time: Thu 2016-02-18 06:02:36 IST
Universal time: Thu 2016-02-18 04:02:36 UTC
RTC time: Thu 2016-02-18 04:02:36
Time zone: Asia/Tel_Aviv (IST, +0200)
NTP enabled: yes
NTP synchronized: no
RTC in local TZ: no
DST active: no
Last DST change: DST ended at
Sun 2015-10-25 01:59:59 IDT
Sun 2015-10-25 01:00:00 IST
Next DST change: DST begins (the clock jumps one hour forward) at
Fri 2016-03-25 01:59:59 IST
Fri 2016-03-25 03:00:00 IDT
(In reply to Alexander Chuzhoy from comment #14) > Depoyed with: > TimeZone: Asia/Tel_Aviv > > And got: > > [root@overcloud-controller-2 ~]# date > Thu Feb 18 06:02:35 IST 2016 > [root@overcloud-controller-2 ~]# timedatectl > Local time: Thu 2016-02-18 06:02:36 IST > Universal time: Thu 2016-02-18 04:02:36 UTC > RTC time: Thu 2016-02-18 04:02:36 > Time zone: Asia/Tel_Aviv (IST, +0200) > NTP enabled: yes > NTP synchronized: no > RTC in local TZ: no > DST active: no > Last DST change: DST ended at > Sun 2015-10-25 01:59:59 IDT > Sun 2015-10-25 01:00:00 IST > Next DST change: DST begins (the clock jumps one hour forward) at > Fri 2016-03-25 01:59:59 IST > Fri 2016-03-25 03:00:00 IDT How did you know what is the correct syntax for the new parameter? It's need to be documented and explain how to use it. I've tried "GMT+2" and "IST" and it did not worked. @Udi, I simply looked under /usr/share/zoneinfo. There's a folder named Asia with Tel_Aviv (amongst others) under it. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-0264.html |