QA:Testcase ABRT kernel addon

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(updated to match current abrt)
 
Line 2: Line 2:
 
|description=This test case tests the functionality of the ABRT kerneloops feature.
 
|description=This test case tests the functionality of the ABRT kerneloops feature.
 
|actions=
 
|actions=
{{admon/note|Syslog|This test abuses syslog a bit - don't forget to restart it at the end of the test case.}}
+
 
 +
 
 +
# Ensure you have will-crash-0.5 installed
 +
#* {{command|su -c 'yum install will-crash-0.5'}}
 
# Ensure you have the plugin installed with the following command:
 
# Ensure you have the plugin installed with the following command:
 
#* {{command|su -c 'yum install abrt-addon-kerneloops'}}
 
#* {{command|su -c 'yum install abrt-addon-kerneloops'}}
 +
# Ensure you have kernel-devel package installed
 +
#* {{command|su -c 'yum install kernel-devel-`uname -r`'}}
 
# Ensure that the system log watcher service is running - {{command|systemctl status abrt-oops.service}}
 
# Ensure that the system log watcher service is running - {{command|systemctl status abrt-oops.service}}
# Download the following file:
 
#* [http://git.fedorahosted.org/cgit/abrt.git/plain/examples/oops1.test oops1.test]
 
 
# Make sure {{filename|/etc/libreport/events.d/koops_event.conf}} contains
 
# Make sure {{filename|/etc/libreport/events.d/koops_event.conf}} contains
#* <tt>EVENT=post-create analyzer=Kerneloops   abrt-action-analyze-oops</tt>
+
<pre>EVENT=post-create analyzer=Kerneloops
#* <tt>EVENT=report_Kerneloops analyzer=Kerneloops reporter-kerneloops</tt>
+
        # >> instead of > is due to bugzilla.redhat.com/show_bug.cgi?id=854266
#* If you have to change anything, restart abrtd: {{command|su -c 'systemctl restart abrtd.service'}}
+
        abrt-action-analyze-oops &&
# Append {{filename|oops1.test}} to {{filename|/var/log/messages}} with the following command:
+
        dmesg >>dmesg &&
#* {{command|su -c 'cat oops1.test >> /var/log/messages'}}
+
        abrt-action-generate-core-backtrace
 +
        abrt-action-save-kernel-data
 +
</pre>
 +
# Run the following command:
 +
#* {{command|su -c 'will_oops'}}
 
# Observe whether a crash notification appears
 
# Observe whether a crash notification appears
 
|results=
 
|results=
 
# ABRT should catch kernel oops appearing in {{filename|/var/log/messages}}, create a crash report and notify you via the notification area
 
# ABRT should catch kernel oops appearing in {{filename|/var/log/messages}}, create a crash report and notify you via the notification area
 
Now restart '''rsyslog''' service so writing to {{filename|/var/log/messages}} works correctly again. Use the following command to restart the service: {{command|su -c 'systemctl restart rsyslog.service'}}.
 
 
 
}}
 
}}
 
[[Category:Package_abrt_test_cases]]
 
[[Category:Package_abrt_test_cases]]

Latest revision as of 12:21, 3 May 2013

Description

This test case tests the functionality of the ABRT kerneloops feature.


How to test

  1. Ensure you have will-crash-0.5 installed
    • su -c 'yum install will-crash-0.5'
  2. Ensure you have the plugin installed with the following command:
    • su -c 'yum install abrt-addon-kerneloops'
  3. Ensure you have kernel-devel package installed
    • su -c 'yum install kernel-devel-`uname -r`'
  4. Ensure that the system log watcher service is running - systemctl status abrt-oops.service
  5. Make sure /etc/libreport/events.d/koops_event.conf contains
EVENT=post-create analyzer=Kerneloops
        # >> instead of > is due to bugzilla.redhat.com/show_bug.cgi?id=854266
        abrt-action-analyze-oops &&
        dmesg >>dmesg &&
        abrt-action-generate-core-backtrace
        abrt-action-save-kernel-data
  1. Run the following command:
    • su -c 'will_oops'
  2. Observe whether a crash notification appears

Expected Results

  1. ABRT should catch kernel oops appearing in /var/log/messages, create a crash report and notify you via the notification area