Red Hat Bugzilla – Bug 430910
timezone exception thrown before any welcome screens
Last modified: 2013-04-12 15:31:24 EDT
Description of problem:
After IPL, an firstboot reported:
"An error has occured in the timezone module..."
before presenting the any of the welcome screens.
Kickstart configured the timezone with:
timezone --utc America/New_York
Traceback (most recent call last):
File "/usr/share/firstboot/firstbootWindow.py", line 496, in loadModules
result = module.launch()
File "/usr/share/firstboot/modules/timezone.py", line 74, in launch
File "/usr/share/firstboot/modules/timezone.py", line 52, in setupScreen
self.timezoneWindow = scdMainWindow.scdMainWindow (firstboot = True,
showPages = ["timezone"])
File "/usr/share/system-config-date/scdMainWindow.py", line 254, in __init__
self.datePage = date_gui.datePage (self.dateBackend, self.xml)
File "/usr/share/system-config-date/date_gui.py", line 57, in __init__
AttributeError: 'NoneType' object has no attribute 'select_month'
We have only seen this error on a system with dual quad cores (8 logical CPUs,
x86_64, 4GB of memory). It might be a race condition that is not encountered
with less CPUs.
Created attachment 293559 [details]
Backported fix from the system-config-date Hg repository.
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".
Proposing for RHEL-5.3 and granting Devel ACK.
Read ya, Phil
Moving to FasTrack actually, fix is really simple and easy to reproduce.
Read ya, Phil
Is there any way how test it on machine with less cpus?
# install system
# rm /etc/sysconfig/firstboot
dont show any problem.
Problems with reproducing bug. Only sanity tests
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.