Description of problem: Reboot test failed when all the tests run together in new v7-1.5-18 test kit on RH6.1 Version-Release number of selected component (if applicable): How reproducible: Install RH6.1 and create the test plan and run all the tests together and Reboot test failed Steps to Reproduce: 1.Install RH6.1x64 2.Install V7-1.5-18 3.Type command line v7 plan 4.Run all the tests together (v7 ceritfy –server xxx.xxx.xxx.xxx) Actual results: Fail Reboot test Expected results: Pass Additional info: - Reboot test failed when all the tests run together. The output.log of Reboot test show method “Panic”. But when you run the Reboot test by itself, it will pass and the output.log show method is “reboot”.
Created attachment 581706 [details] Reboot test run together log
Created attachment 581708 [details] Reboot test run by itself log
Please attach /var/v7/results.xml
Created attachment 581969 [details] Logs
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: An enhancement is made in v7 1.5 that `reboot` test is no more automatically scheduled when executing `v7 plan`, due to the functionality has been replaced by `kdump` test.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -An enhancement is made in v7 1.5 that `reboot` test is no more automatically scheduled when executing `v7 plan`, due to the functionality has been replaced by `kdump` test.+An enhancement is made in v7 1.5 that `reboot` test is no more automatically scheduled when executing `v7 plan`, due to the functionality has been replaced by `kdump` test. A user should still be able to add `reboot` test manually with '--add' option.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0711.html