Bug 902608

Summary: Anaconda reports "An unknown error has occurred" and then freezes
Product: [Fedora] Fedora Reporter: Andrew McNabb <amcnabb>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 18CC: anaconda-maint-list, g.kaviyarasu, jonathan, sbueno, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-24 15:32:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
anaconda.log
none
program.log
none
storage.log none

Description Andrew McNabb 2013-01-22 04:46:39 UTC 
Immediately upon entering Anaconda (during a netboot install), it reports:

"""An unknown error has occurred

This program has encountered an unknown error. You may
report the bug below or quit the program.
"""

I can move the mouse, but I cannot click on the "More info...", "Report Bug", or "Quit" buttons. Anaconda does not show any response to trying to click on any of these buttons.  If I switch to a VT and then switch back to Anaconda, I see a gray box in the middle of the screen, but neither the error message nor the buttons appear in the box. Meanwhile, top reports that anaconda is using 100% CPU. None of the logs on VTs 3, 4, or 5 give any clear indication of what is causing the hang. I've let it go at least 10 minutes without any response.

In anaconda.log, the last message is "All kickstart %%traceback script(s) have been run". The last line in storage.log is "resize2fs: Device or resource busy while trying to open /dev/loop1". I'm not sure whether either of these messages is related. I will attach the full logs to this report.
Comment 1 Andrew McNabb 2013-01-22 04:47:30 UTC 
Created attachment 684839 [details]
anaconda.log
Comment 2 Andrew McNabb 2013-01-22 04:47:55 UTC 
Created attachment 684840 [details]
program.log
Comment 3 Andrew McNabb 2013-01-22 04:48:17 UTC 
Created attachment 684841 [details]
storage.log
Comment 4 Andrew McNabb 2013-01-22 04:56:33 UTC 
I manually powered off all but the first hard drive (sda), and this seems to allow Anaconda to start. So it seems that maybe it's crashing in response to something on the other disks.
Comment 5 Chris Lumens 2013-01-22 16:12:41 UTC 
Is there no /tmp/anaconda-tb-* file?  This is pretty weird.
Comment 6 Andrew McNabb 2013-01-22 16:59:08 UTC 
I don't know whether there was a /tmp/anaconda-tb-* file, because it wasn't something I knew to look for. I copied out *.log, so if anaconda-tb-* has a .log extension, then the traceback file didn't exist. And given the hang using 100% CPU, it's very possible that anaconda ran away while trying to write the file.
Comment 7 Chris Lumens 2013-01-24 15:32:55 UTC 
Without /tmp/anaconda-tb-*, we're not going to be able to do any debugging here.  I don't see anything in your attached log files that's incriminating.  If you're able to reproduce, feel free to reopen.
Comment 8 Andrew McNabb 2013-01-24 16:54:19 UTC 
The fact that turning off hard drives made anaconda work is critical information. And clearly, using 100% CPU is a bug independent of whatever traceback may have happened. I really think there's a lot of information here, and I believe it's very likely that the anaconda-tb-* were never created due to the hang in Anaconda.