Description of problem: During a rawhide acceptance test run (using install.py [1]), a storage activation error was encountered. Since this is an automated kickstart test, it monitors for /tmp/anacdump.txt and appropriately fails the test if such a file exists. In this case, no dump file was created. Instead, the user was prompted during the kickstart install as to whether they wanted to file a bug or not. If the subsequent traceback is needed for diagnosing the root cause of this failure, I'd like to request that for automated kickstart installs, the user is not prompted to write a kickstart file. Instead, it is saved directly to /tmp/anacdump.txt [1] http://git.fedorahosted.org/git/autoqa.git?p=autoqa.git;a=blob;f=tests/rats_install/install.py;hb=HEAD Version-Release number of selected component (if applicable): * anaconda-13.22-1.fc13 How reproducible: * This doesn't seem like a common storage bug, I haven't seen it since, but this issue is meant more to track the failure behavior for this class of storage issues. Steps to Reproduce: 1. Initiate a rats_install/install.py test $ python install.py -a x86_64 http://alt.fedoraproject.org/pub/alt/stage/rawhide/x86_64/os Or, just install using the following details * stage2=http://alt.fedoraproject.org/pub/alt/stage/rawhide/x86_64/os * repo=http://download.fedoraproject.org/pub/fedora/linux/development/x86_64/os * updates=http://jlaska.fedorapeople.org/updates-557588.img * ks=http://git.fedorahosted.org/git/autoqa.git?p=autoqa.git;a=blob;f=tests/rats_install/ks.cfg;h=0fa5954c08431ca3562605eb8ca2a2bfcd5e00e4;hb=HEAD Actual results: ┌─────────────────────┤ Storage Activation Failed ├─────────────────────┐ │ │ │ An error was encountered while activating your storage configuration. │ │ │ │ (root@dell-t5400)-(7/pts/5)-(01/22/2010 11:50am)-8 INFO : ↑ │ (~)> Running... ['lvm', 'lvcreate', '-L', '6760m', '-n', ▮ │ │ 'lv_root', 'VolGroup'] ▒ │ │ ▒ │ │ ▒ │ │ ↓ │ │ │ │ ┌──────────┐ ┌────────────────┐ │ │ │ File Bug │ │ Exit installer │ │ │ └──────────┘ └────────────────┘ │ │ │ │ │ └───────────────────────────────────────────────────────────────────────┘ Expected results: For a kickstart install, if a failure occurs I expected it to automatically record the traceback locally as /tmp/anacdump.txt. Additional info:
Agreed at blocker bug review of 2010-02-05 that this is not an Alpha blocker.
I've updated the error handling here to make almost all storage exceptions fatal errors that will result in the usual exception handling dialog appear. However there are still certain cases where the error is not due to an anaconda bug, and those will still cause the more generic dialog to appear. The intention here is to not make those look like anaconda bugs.