QA:Testcase Anaconda save traceback to bugzilla

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.

Description

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. A valid bugzilla username and password is required for this test, please refer to BugsAndFeatureRequests.

Setup

Download and prepare any Fedora installation medium.

How to test

How to test on Anaconda's GTK version or text version

1. Boot the installer by any available means.
   • If you want to boot the installer in the text mode, hit TAB in the boot menu and add inst.text into the command prompt. This option is not available for the Live images.
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 as root:

   kill -USR1 `cat /var/run/anaconda.pid`

   Switch back to the installer, an error prompt should be displayed after a few seconds (you might need to click on some UI element to achieve that, or 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. After the bug has been reported, go to Bugzilla, inspect that description and attachments were created correctly, and close the bug as NOTABUG.

How to test on Anaconda WebUI

1. Boot from the Fedora Workstation or KDE Live ISO image.
2. Wait, until Anaconda WebUI is fully started, set a language and click Continue.
3. Access the Console:
   1. On Workstation (GNOME): Open the Activities Overview by pressing the Super key (Windows key) or moving your cursor to the top-left corner of the screen. Launch the Terminal app.
   2. On KDE: Open the application launcher by pressing the Super key (Windows key) and search for Konsole.
4. Run the command sudo rm -f /run/anaconda/backend_ready to trigger the Anaconda testing feature for the error reporting dialog.
5. Use the Error dialog to report the error to Bugzilla. Use "Testing, please ignore" as the title of the bug, so that developers know that they don't need to pay attention to it.
6. After the bug has been reported, go to Bugzilla, inspect that description and attachments were created correctly, and close the 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.