QA:Testcase ABRT vmcore

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(remove fedora 17 warning, some reformatting)
Line 9: Line 9:
 
# Ensure that the system log watcher service is running - {{command|systemctl status abrt-vmcore.service}}
 
# Ensure that the system log watcher service is running - {{command|systemctl status abrt-vmcore.service}}
 
#* If you have to change anything, restart abrtd: {{command|su -c 'systemctl restart abrtd.service'}}
 
#* If you have to change anything, restart abrtd: {{command|su -c 'systemctl restart abrtd.service'}}
{{admon/warning|System-config-kdump is broken in Fedora 17 - edit /etc/default/grub instead, then run grub2-mkconfig > /etc/grub2.cfg}}
+
# Add <code>crashkernel=128M</code> to kernel command line.
# Add "crashkernel=128M" to kernel command line (say, via system-config-kdump -> "Enable", "Apply").  
+
#* You can either use system-config-kdump, click "Enable" and then "Apply".
 +
#* Or you can manually edit {{filename|/etc/default/grub}} and then re-generate grub configuration file.
 
# Reboot.
 
# Reboot.
 
# Ensure that the kdump service is running - {{command|systemctl status kdump.service}}. If it doesn't, no vmcore will be saved on crash.
 
# Ensure that the kdump service is running - {{command|systemctl status kdump.service}}. If it doesn't, no vmcore will be saved on crash.
 
# Crash the machine: {{command|sync; echo 1 >/proc/sys/kernel/sysrq; echo c >/proc/sysrq-trigger}}
 
# Crash the machine: {{command|sync; echo 1 >/proc/sys/kernel/sysrq; echo c >/proc/sysrq-trigger}}
# When rebooting after kernel panic ABRT should detect the new vmcore appearing in {{filename|/var/crash}}, create a crash report and notify
+
# When rebooting after kernel panic ABRT should detect the new vmcore appearing in {{filename|/var/crash}}, create a crash report and notify you via the notification area
you via the notification area
+
 
}}
 
}}
 
[[Category:Package_abrt_test_cases]]
 
[[Category:Package_abrt_test_cases]]

Revision as of 08:55, 6 May 2013

Description

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


How to test

Note.png
Please note that this test probably can't be done using live cd.
  1. Ensure you have the plugin installed with the following command:
    • su -c 'yum install abrt-addon-vmcore'
  2. Ensure you have necessary packages for producing vmcore and its processing:
    • su -c 'yum install kexec-tools crash system-config-kdump'
  3. Ensure that the system log watcher service is running - systemctl status abrt-vmcore.service
    • If you have to change anything, restart abrtd: su -c 'systemctl restart abrtd.service'
  4. Add crashkernel=128M to kernel command line.
    • You can either use system-config-kdump, click "Enable" and then "Apply".
    • Or you can manually edit /etc/default/grub and then re-generate grub configuration file.
  5. Reboot.
  6. Ensure that the kdump service is running - systemctl status kdump.service. If it doesn't, no vmcore will be saved on crash.
  7. Crash the machine: sync; echo 1 >/proc/sys/kernel/sysrq; echo c >/proc/sysrq-trigger
  8. When rebooting after kernel panic ABRT should detect the new vmcore appearing in /var/crash, create a crash report and notify you via the notification area

Expected Results

  1. Step #1 completes without error
  2. The system boots into runlevel 5
  3. Program completes with exit code 0