Hide Forgot
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
Created attachment 531456 [details] Reboot test
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.
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).
Created attachment 532922 [details] v7 error
Created attachment 532923 [details] PS output
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.
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?
Correct.
Created attachment 534313 [details] rpm file
(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
Yes. This is still an issue with v7-1.5-32 test kit version on RH5.7x86 and x64.
(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?