Latest revision as of 13:07, 25 February 2025

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

Boot the installer by any available means.
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.
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).
Check that a file with all the crash details has been created in /tmp/anaconda-tb-*.
Report the exception to Bugzilla using the error prompt.

How to test on Anaconda WebUI

Boot the Fedora Workstation Live iso image. In Fedora 42, this option is only available on Workstation.
Wait, until Anaconda WebUI is fully started, set a language and click Continue.
Press F12 to open development tools of the browser window.
On the console pane, write the command window.setTimeout(function() { myNonExistingFunction()}, 0) and press Enter
Use the Error dialog to report the error to Bugzilla.

After the bug has been reported, go to Bugzilla and close the bug as NOTABUG.

Expected Results

The installer presents a failure prompt and allows you to report it to Bugzilla.
Exception traceback is displayed.
Crash details are saved into /tmp/anaconda-tb-*.
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.
Details of the failure are attached to the bug report.

@@ Line 1: / Line 1: @@
+{{Template:Associated_release_criterion|Alpha|failure-reporting}}
 {{QA/Test_Case
-|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 [http://jlaska.fedorapeople.org/updates/traceback.img 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]].
+|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, or [[How_to_build_a_Rawhide_ISO_image_for_testing|create]], boot media needed to boot and test the Fedora installer
+|setup=Download and prepare any Fedora installation medium.
 |actions=
-# Boot the installer by any available means (CD, DVD, boot.iso or PXE).  When booting, you must direct the installer towards an [http://jlaska.fedorapeople.org/updates/traceback.img updates.img] using one of the methods below.
+===How to test on Anaconda's GTK version or text version===
-#* To trigger a failure which is already recorded in bugzilla, add the following boot parameter <pre>updates=http://jlaska.fedorapeople.org/updates/traceback.img</pre>
+# Boot the installer by any available means.
-#* To trigger a new failure and have the installer create a new bugzilla, add the following boot parameters <pre>updates=http://jlaska.fedorapeople.org/updates/traceback.img randomize_tb</pre>
+# To boot the installer in the text mode, hit TAB in the boot menu and add <code>inst.text</code> into the command prompt. This option is not available for the Live images.
-# When prompted, make language and keyboard selections.
+# If you know how to make Anaconda crash, you can do so. Otherwise use Anaconda's [http://lists.fedoraproject.org/pipermail/test/2012-September/110149.html fake exception handling trigger] - switch to a different terminal and run the following command as root: <pre>kill -USR1 `cat /var/run/anaconda.pid`</pre> 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).
-# Depending on your installation method, you maybe prompted for a remote installation source.  Make a selection and continue.
+# Check that a file with all the crash details has been created in {{filename|/tmp/anaconda-tb-*}}.
-# Upon entering [http://fedoraproject.org/wiki/Anaconda/Stage stage2] of the installer, you will be presented with a failure dialog.  Select '''Save'''
+# Report the exception to Bugzilla using the error prompt.
-# On the following dialog, choose '''bugzilla.redhat.com''' from the destination list.
+===How to test on Anaconda WebUI===
-# Enter a valid bugzilla ''username'' and ''password'', and select '''OK'''.
+# Boot the Fedora Workstation Live iso image. In Fedora 42, this option is only available on Workstation.
+# Wait, until Anaconda WebUI is fully started, set a language and click Continue.
+# Press '''F12''' to open development tools of the browser window.
+# On the console pane, write the command `window.setTimeout(function() { myNonExistingFunction()}, 0)` and press '''Enter'''
+# Use the Error dialog to report the error to Bugzilla.
+After the bug has been reported,  go to Bugzilla and close the bug as '''NOTABUG'''.
 |results=
-# The installer presents a failure dialog and offers an option to save the failure report.
+# The installer presents a failure prompt and allows you to report it to Bugzilla.
-# The ''Bug description'' is pre-populated with information about the traceback.
+# Exception traceback is displayed.
-# 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
+# Crash details are saved into {{filename|/tmp/anaconda-tb-*}}.
-# Details of the failure are attached to the bug report
+# 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.
+# Details of the failure are attached to the bug report.
 }}
 [[Category:Recovery Test Cases]]
 [[Category:Package_report_test_cases]]

Search

QA:Testcase Anaconda save traceback to bugzilla: Difference between revisions