Hide Forgot
Currently, reboot test will pass even though kdump is not running. But it's not what we should expect. Please fail reboot test when kdump is not running. Belowing is the result of sample output: https://hardware.redhat.com/results.cgi?cert_id=711310&id=230845 ====================================== <output> Running ./reboot.py: Checking kdump configuration Warning: "crashkernel" is not set in boot parameters Kernel panic reboot timeout is 0 Setting to 1 sec. Checking kdump service Warning: kdump is not running - can not test it "service kdump status" no match for regular expression is operational The system must be restarted for this test Ready to restart? (yn) response: y Syncing disks Waiting for low load... Current load average: 0.9 Done waiting <output> Running ./reboot.py: reboot took 00:03:00 Jun 13 13:55:52 1026T-URF-x86 kernel: Linux version 2.6.32-71.el6.i686 (mockbuild.bos.redhat.com) (gcc version 4.4.4 20100726 (Red Hat 4.4.4-13) (GCC) ) #1 SMP Wed Sep 1 01:26:34 EDT 2010 reboot verified ...finished running ./reboot.py, exit code=0 </output> 315900024632489420052854074478034467178
I'm going to go ahead and close this duplicate of bug 718290. The net result of that change would be reboot would only test reboot and thus should pass without kdump and the kdump test would test only kdump and should thus fail without kdump. *** This bug has been marked as a duplicate of bug 718290 ***