Bug 50429
| Summary: | ksconfig crashes if timezone not in zone.tab | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Steve Bonneville <sbonnevi> |
| Component: | ksconfig | Assignee: | Brent Fox <bfox> |
| Status: | CLOSED RAWHIDE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.1 | CC: | rreed |
| 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: | 2001-07-31 03:21:00 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: | |||
Fixed in cvs. It's also available in the Roswell public beta. |
Description of Problem: If the ZONE variable in /etc/sysconfig/clock is set to a valid timezone in /usr/share/zoneinfo that is NOT also in /usr/share/zoneinfo/zone.tab, then ksconfig crashes with an ugly Python error. How Reproducible: always Steps to Reproduce: 1. Set ZONE="US/Central" in /etc/sysconfig/clock 2. Run ksconfig. If you set ZONE="America/Chicago", ksconfig magically works again. Actual Results: Traceback (innermost last): File "/usr/share/ksconfig/ksconfig.py", line 387, in ? timeCombo.list.select_item(select) NameError: select Expected Results: ksconfig should run normally, no matter what value is in /etc/sysconfig/clock. Preferably, there should be a way to set the timezone value in ksconfig. Additional Information: It's not clear to me that zone.tab is meant to list ALL valid timezones on the system. If it is, then we have a bug in glibc-common as well, and possibly anaconda.