Red Hat Bugzilla – Bug 77078
firstboot tracebacks on a dirty system
Last modified: 2008-05-01 11:38:04 EDT
Description of Problem: firstboot tracebacks with: Traceback (most recent call last): File "/usr/share/firstboot/firstbootWindow.py", line 151, in __init__ vbox, eventbox = module.launch() File "/usr/share/firstboot/modules/date.py", line 75, in launch self.setupScreen() File "/usr/share/firstboot/modules/date.py", line 64, in setupScreen self.datePage = date_gui.datePage(self.dateBackend) File "/usr/share/redhat-config-date/date_gui.py", line 149, in __init__ ntpStatus = mainWindow.dateBackend.isNtpRunning() File "/usr/share/redhat-config-date/dateBackend.py", line 163, in isNtpRunning line = output[0] IndexError: list index out of range The traceback occurs in an X11 window, then saved to a file in ~root. Version-Release number of selected component (if applicable): firstboot-1.0.1-10 How Reproducible: Unknown Steps to Reproduce: 1. Install and configure text login (e.g. init level 3), configure stuff, etc. 2. Edit /etc/inittab and change default runlevel to 5 3. Reboot with <ctrl-alt-del> Actual Results: Traceback Expected Results: Working Additional Information: I think the firstboot might have been confused by running on top of an "unclean" system which was in operation for a while, so it's not really the "first" boot.
Can you attach /etc/ntp.conf? It looks like something in that file is a breaking the parser.
Created attachment 85486 [details] /etc/ntp.conf @mellorn.sfbay.redhat.com
Indeed, I changed ntp.conf on that box. Look at the line: server clock2.corp.redhat.com
I'm sorry. The code isn't breaking in the file parser, it's with trying to parse the return value of the ntp init script. Please try running '/sbin/service ntpd stats' and attach the output to the report.
[zaitcev@mellorn zaitcev]$ service ntpd stats Usage: /etc/init.d/ntpd {start|stop|restart|condrestart|status} [zaitcev@mellorn zaitcev]$ service ntpd status ntpd (pid 725) is running... [zaitcev@mellorn zaitcev]$
I've changed the isNtpRunning function to check the return value of the initscript instead of trying to parse the output of the initscript, so this shouldn't happen anymore. Please reopen if you see this behavior in Phoebe, but I'm reasonably certain that this bug has been fixed. QA, please verify with redhat-config-date-1.5.9-1.
There is a stack of 64 bugs that have been in Modified state for a long period of time. I am closing these as Rawhide now. If you find that the issue is not fixed, please reopen this report.