Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionBrendan McGrath
2016-12-10 07:19:00 UTC
Description of problem:
system-config-date puts 'Los Angeles' in /etc/sysconfig/clock
Version-Release number of selected component (if applicable):
1.9.60-2.el6.centos
How reproducible:
Every time you run system-config-date and select 'Los Angeles'.
Steps to Reproduce:
1. Run system-config-date
2. Select Los Angeles under TimeZone
3. Press OK
Actual results:
Content of /etc/sysconfig/clock is:
# The time zone of the system is defined by the contents of /etc/localtime.
# This file is only for evaluation by system-config-date, do not rely on its
# contents elsewhere.
ZONE="America/Los Angeles"
Expected results:
Content of /etc/sysconfig/clock is:
# The time zone of the system is defined by the contents of /etc/localtime.
# This file is only for evaluation by system-config-date, do not rely on its
# contents elsewhere.
ZONE="America/Los_Angeles"
Additional info:
The content of the "ZONE" variable should match the file name in /usr/share/zoneinfo/ - which is /usr/share/zoneinfo/America/Los_Angeles. When this does not match - an update of the tzdata package does not update /etc/localtime.
The fix appears to be a one liner:
diff --git a/src/scdate/core/timezoneBackend.py b/src/scdate/core/timezoneBackend.py
index 806aaaa..605f2fa 100644
--- a/src/scdate/core/timezoneBackend.py
+++ b/src/scdate/core/timezoneBackend.py
@@ -56,7 +56,7 @@ class timezoneBackend(object):
f.write ("# The time zone of the system is defined by the contents of /etc/localtime.\n")
f.write ("# This file is only for evaluation by system-config-date, do not rely on its\n")
f.write ("# contents elsewhere.\n")
- f.write('ZONE="%s"\n' % timezone)
+ f.write('ZONE="%s"\n' % timezonefile)
f.close()
if self._adjtimeHasUTCInfo:
Thanks for confirming this will be in the next minor version of RHEL.
Unfortunately I can't access bug 956284 so I have a few follow up questions.
Are you able to advise when the next minor version of RHEL will be released (I assume you are referring to RHEL 6.9)?
Also - I would like to review the patch used to fix this and potentially apply it manually in advance. Or is the plan to migrate to version 1.10 (which appears to take a different approach).
Thanks again. And given bug 956284 is not public - this information could be useful for the next person.
(In reply to Brendan McGrath from comment #5)
> Thanks for confirming this will be in the next minor version of RHEL.
>
> Unfortunately I can't access bug 956284 so I have a few follow up questions.
>
> Are you able to advise when the next minor version of RHEL will be released
> (I assume you are referring to RHEL 6.9)?
I'm not allowed to do that, sorry.
> Also - I would like to review the patch used to fix this and potentially
> apply it manually in advance. Or is the plan to migrate to version 1.10
> (which appears to take a different approach).
You can apply the patch from comment#1. There's no plan to migrate to other versions.