From Fedora Project Wiki

Associated release criterion
This test case is associated with the Basic_Release_Criteria#failure-reporting release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.


This test case is intended to introduce a failure, and validate Anaconda is able to properly handle the failure and report the issue to bugzilla while running in Text mode. A valid bugzilla username and password are required for this test, please refer to BugsAndFeatureRequests.


Download and prepare any Fedora installation medium.

How to test

  1. If you're using a non-Live installation medium, boot the installer and add inst.text to the boot options; otherwise for Live media you have to start the installer manually from terminal liveinst --text
  2. If you know how to make Anaconda crash, you can do so. Otherwise use Anaconda's fake exception handling trigger - switch to a different terminal and run the following command:
    kill -USR1 `cat /var/run/`
    Switch back to the installer, an error prompt should be displayed after a few seconds (you might need to hit refresh in a text mode).
  3. Check that a file with all the crash details has been created in /tmp/anaconda-tb-*.
  4. Report the exception to Bugzilla using the error prompt.
  5. If you used the fake exception handling trigger, go to Bugzilla and close the newly reported bug as NOTABUG.

Expected Results

  1. The installer presents a failure prompt and allows you to report it to Bugzilla.
  2. Exception traceback is displayed.
  3. Crash details are saved into /tmp/anaconda-tb-*.
  4. After reporting to Bugzilla, depending on the traceback you are either informed that a new bug was created, or that an existing bug was found that matches this failure. Either way, a bug number is provided.
  5. Details of the failure are attached to the bug report.