Bug 697863

Summary: multiple reboot tests are not run correctly
Product: [Retired] Red Hat Hardware Certification Program Reporter: Greg Nichols <gnichols>
Component: Test Suite (tests)Assignee: Greg Nichols <gnichols>
Status: CLOSED ERRATA QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.3CC: czhang, rlandry, ykun, yuchen
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-09 16:12:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
hardwaretest.py patch fixing order of reboot tests
none
continuation.py patch to allow reboot test to determine initializatoin state
none
reboot.py patch to check if continuation has initialized
none
continuation.py patch to allow reboot test to determine initialization state none

Description Greg Nichols 2011-04-19 13:32:39 UTC
Description of problem:

If multiple reboot tests are attempted within the same run, v7 does not plan the order of the tests correctly.   

v7 run --test reboot

results in the following order:

reboot local
info
reboot local

The test run completes as:

info
reboot local

(nfs does not run).

It should use the following order:

info
reboot local
reboot nfs

(or nfs, followed by local, so long as the reboot tests run last)


Version-Release number of selected component (if applicable):

v7 1.3 R33

Comment 1 Greg Nichols 2011-04-19 13:34:32 UTC
Created attachment 493194 [details]
hardwaretest.py patch fixing order of reboot tests

Comment 2 Greg Nichols 2011-04-19 13:36:30 UTC
Created attachment 493195 [details]
continuation.py patch to allow reboot test to determine initializatoin state

This patch changes test continuation so that it cleans up (deletes) the bootstamp file when finishing in incomplete test.  This allows subsequent tests using continuations to determine if they have been initialized.

Comment 3 Greg Nichols 2011-04-19 13:38:11 UTC
Created attachment 493196 [details]
reboot.py patch to check if continuation has initialized

Comment 4 Greg Nichols 2011-04-19 13:43:21 UTC
Created attachment 493202 [details]
continuation.py patch to allow reboot test to determine initialization state

Comment 7 chen yuwen 2011-04-28 05:16:13 UTC
Reproduced on R33

[root@hp-dl180g6-01 ~]# v7 run -t reboot
loaded results /var/v7/results.xml
Tested OS: Red Hat Enterprise Linux Server 6.1 (Santiago)
Kernel RPM: kernel-2.6.32-112.el6
v7 version 1.3, release 33
saved test plan to /var/v7/results.xml

Running the following tests:
reboot     local                                          
info                                                      
reboot     local     

Test Verification Passed
Run these tests? (y|n) y
response: y
reboot     local                                           
info                                                       
reboot     local                                            
...


Verified on R37

[root@hp-dl180g6-01 ~]# v7 run -t reboot
loaded results /var/v7/results.xml
Tested OS: Red Hat Enterprise Linux Server 6.1 (Santiago)
Kernel RPM: kernel-2.6.32-112.el6
v7 version 1.3, release 37
saved test plan to /var/v7/results.xml

Running the following tests:
info                                                      
reboot     nfs                                            
reboot     local                                          

Test Verification Passed
Run these tests? (y|n) y
response: y
info                                                       
reboot     nfs                                             
reboot     local   
...

Comment 8 Caspar Zhang 2011-05-01 10:11:05 UTC
This bug does not need a Tech Note because of:

1. A Red Hatter reported it
2. It only happened in an intermediate version.

Comment 9 errata-xmlrpc 2011-05-09 16:12:10 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0497.html