QA:Testcase Anaconda save traceback to bugzilla

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. This test case relies on an updates.img that will intentionally cause the installation to fail in a manner that is non-destructive to your existing system. For more information in using an updates.img, see Anaconda/Updates. A valid bugzilla username and password is required for this test, please refer to BugsAndFeatureRequests.

How to test

1. Boot the installer by any available means (CD, DVD, boot.iso or PXE). When booting, you must direct the installer towards an updates.img using one of the methods below.
   • To trigger a failure which is already recorded in bugzilla, add the following boot parameter

     updates=http://jlaska.fedorapeople.org/traceback.img

   • To trigger a new failure and have the installer create a new bugzilla, add the following boot parameters

     updates=http://jlaska.fedorapeople.org/traceback.img randomize_tb

2. If you also wish to test
3. When prompted, make language and keyboard selections.
4. Depending on your installation method, you maybe prompted for a remote installation source. Make a selection and continue.
5. Upon entering stage2 of the installer, you will be presented with a failure dialog. Select Save
6. On the Save dialog, choose Bugzilla from the destination list.
7. Enter a valid bugzilla username and password, and select OK.

Expected Results

1. The installer presents a failure dialog and offers an option to save the failure report.
2. The Bug description is pre-populated with information about the traceback.
3. Depending on the traceback, you are informed that a new bug was created, or that an existing bug was found that matches this failure. Either way, a bug# is provided
4. Details of the failure are attached to the bug report