Description of problem: I found that all kdump test cases failed in setup-bare-metal, which would reboot system once before it finish. The system will reboot again and again then timeout. https://beaker.engineering.redhat.com/jobs/92832 Version-Release number of selected component (if applicable): 0.6.12-1 How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
rhts-compat service did not come up. Testing a fix preventing infinite loop in such case.
Run jobs rebooting and simulating error conditions leading to possible infinite loop without troubles (except not working rhts-compat - will look at that later) After packages are brewed, I will deploy on stage for common consumption and then get it synced to beaker.
Can we solve the " ./rhts-compat/not-running " warnings? All jobs completed in a non-success status.
I have an un-official solution on beaker-stage. <repo name="beaker-harness" url="http://beaker-stage.app.eng.bos.redhat.com/harness/epel-5/"/> That allows rhts-compat to run after reboot and without the warnings.
I am testing the official solution. Looks well. Thanks to bpeck and jburke for their valuable help in diagnosing the problem!
Minimal fix available ot stage: <repo name="beaker-harness" url="http://beaker-stage.app.eng.bos.redhat.com/harness/epel-5/"/> No more warnings; no more infinite-reboots.
Marian, Kdump test cases have some problem with new beaker packages. Please see https://beaker.engineering.redhat.com/recipes/194107 After triggering system crash and reboot back, system cannot connet to beaker sever and all remaining cases failed. Please have a look. Thanks.
Deployed. Re(In reply to comment #12) > Marian, > > Kdump test cases have some problem with new beaker packages. Please see > > https://beaker.engineering.redhat.com/recipes/194107 > > After triggering system crash and reboot back, system cannot connet to beaker > sever and all remaining cases failed. Please have a look. Thanks. Yes, I mentioned that in comment #11 - looks like widespread issue. May be related to the problem with rc.sysinit on latest rhel5.7 not deleting lock files on boot which among other things prevent sshd from starting. bpeck: Have you opened a BZ? You can try connecting to console and while booting edit kernel options to enter into runlevel 1 (add 1 to the end of the line) [1] and then it's in your hand to find the problem and report/fix :-( [1] Alternatively you can pass an option to the task blocking to have an access to console: https://engineering.redhat.com/trac/rhts/wiki/TestMakefile#RhtsOptions
bpeck: Found. Closed as duplicate: https://bugzilla.redhat.com/show_bug.cgi?id=711826
Han Pingtian , The issue is with the distro. Consider it busted. Use RHEL5.7-Server-20110608.1 instead.