Bug 750941

Summary: Reboot test dose not complete with test kit v7.1-4.36 in RH5.7x64
Product: [Retired] Red Hat Hardware Certification Program Reporter: chau nguyen <chau.nguyen2>
Component: Test Suite (tests)Assignee: Caspar Zhang <czhang>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 6.0CC: chau.nguyen2, czhang, gbai, gnichols, gregg.shick, gwen.lapo, qcai, rlandry
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-10-23 19:11:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 767775, 773757    
Attachments:
Description Flags
Reboot test
none
v7 error
none
PS output
none
rpm file none

Description chau nguyen 2011-11-02 21:47:45 UTC 
Description of problem:  Reboot test dose not complete with test kit v7.1-4.36 in RH5.7x64


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


How reproducible:
Select Reboot test from test kits and type yes to allow the system reboot.  Once the system boot up wait for ten minutes and open terminal and type “v7 print” and error message display “Error: v7 is already running”.  The v7 is never stopping run.

Steps to Reproduce:
1.Install RH5.7x64
2.Install test kit version v7.1-4.36
3.Run the reboot test only
4.V7 is never stopping run
  
Actual results:
V7 is never stopping run

Expected results:
Pass

Additional info:
Please check out screen shot
Comment 1 chau nguyen 2011-11-02 21:48:20 UTC 
Created attachment 531456 [details]
Reboot test
Comment 2 Rob Landry 2011-11-09 20:24:44 UTC 
Does top/ps etc. show that v7 is running?

If yes, will need to know what it's up to.

If not, that means a stale lock is remaining from some event.  The logs from v7 will be needed to investigate.
Comment 3 chau nguyen 2011-11-10 20:30:45 UTC 
Please see attached logs. 

V7 is still showing locked after 2 hours. Top doesn’t show a v7 process, neither does ps (please see attached ps output).
Comment 4 chau nguyen 2011-11-10 20:32:21 UTC 
Created attachment 532922 [details]
v7 error
Comment 5 chau nguyen 2011-11-10 20:32:45 UTC 
Created attachment 532923 [details]
PS output
Comment 6 Rob Landry 2011-11-16 17:57:38 UTC 
Can the results rpm be attached, we can check in the sosreport ot see if there's any sort of startup failures from the initscript.  It does look like an orphaned lock file is the error so the question is what got us there.  Clearning the lock should allow the package to be built.
Comment 7 chau nguyen 2011-11-16 20:32:00 UTC 
Just want to confirm.  You want me to package with v7 submit and when it warns about the lock you want me to choose y to kill the lock. Correct?
Comment 8 Rob Landry 2011-11-16 20:39:24 UTC 
Correct.
Comment 9 chau nguyen 2011-11-17 20:34:59 UTC 
Created attachment 534313 [details]
rpm file
Comment 17 Rob Landry 2012-08-06 18:21:10 UTC 
(In reply to comment #9)
> Created attachment 534313 [details]
> rpm file

Hi Chau,

Is this still an issue with the 1.5 test suite?  Technically reboot is not required on RHEL5, so this is not a certification blocker however I also wanted to check if this was still an issue is there a use case for it where it would make sense to investigate this?

Thanks,

-Rob
Comment 18 chau nguyen 2012-08-10 15:00:07 UTC 
Yes.  This is still an issue with v7-1.5-32 test kit version on RH5.7x86 and x64.
Comment 19 Rob Landry 2012-08-10 15:29:29 UTC 
(In reply to comment #18)
> Yes.  This is still an issue with v7-1.5-32 test kit version on RH5.7x86 and
> x64.

Hi Chau,

Given reboot is not required for certification, is the use case that it's scheduled by default but also not working causing additional work in disabling it, and/or is there another use case where the reboot test could prove useful except that it is not working on RHEL5?