Bug 73688
Summary: | redhat-config-[date|time] fails with a pyhton traceback | ||
---|---|---|---|
Product: | [Retired] Red Hat Public Beta | Reporter: | adam allen <adamallen> |
Component: | dateconfig | Assignee: | Brent Fox <bfox> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | null | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-10-15 02:52:57 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
adam allen
2002-09-08 21:15:10 UTC
A couple of questions. 1) Was this an upgrade from a previous release? 2) What does your /etc/sysconfig/clock file look like? Version: redhat-config-date-1.5.2-9 Fresh install of null, with all relevant up2date applied the day the bug was reported. On a seperate install of null on another machine- without any updates redhat-config-date worked. After updated redhat-config-date stopped working. Dropping down to redhat-config-date-1.5.1-2 and the utility launches without any errors. /etc/sysconfig/clock ZONE="GB" UTC=true ARC=false Um, how did you get ZONE="GB" in /etc/sysconfig/clock? That is not a valid timezone according to /usr/share/zoneinfo/zone.tab. I think "Europe/London" is what you're looking for. However, redhat-config-date should not crash on an invalid timezone. This should be fixed with redhat-config-date-1.5.3-1 which should apprear in Rawhide in the next day or so. If this doesn't fix the problem, please reopen this bug report. |