- the /tmp may not persist the reboot/test - root should not write to /tmp (or at least I was told selinux does not like that) - some tests require limited space on /tmp partition
This is starting to be an issue with recent RHEL7 nightly trees, because /tmp is mounted as tmpfs and it goes away after each reboot: Bug 810515 - tmpfs as default filesystem on /tmp For example when kernelinstall makes reboot task aborts with: Upon execvpe /tmp/tmpnhFd4I.sh ['/tmp/tmpnhFd4I.sh', 'distribution-distribution-kernelinstall'] in environment id 43387024 :Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/twisted/internet/process.py", line 414, in _fork executable, args, environment) File "/usr/lib64/python2.7/site-packages/twisted/internet/process.py", line 460, in _execChild os.execvpe(executable, args, environment) File "/usr/lib64/python2.7/os.py", line 353, in execvpe _execvpe(file, args, env) File "/usr/lib64/python2.7/os.py", line 368, in _execvpe func(file, *argrest) OSError: [Errno 2] No such file or directory
Minjung, I have bumped the Severity and the Priority of this BZ. This is becoming a blocking issue. Can we take this BZ of of future_maint? Thanks, Jeff
http://gerrit.beaker-project.org/#/c/1403/
Jeff, I proposed this to be in Beaker 0.10 which is currently scheduled to be released in week 47. Is this enough for your need?
*** Bug 668763 has been marked as a duplicate of this bug. ***
Bulk reassignment of issues as Bill has moved to another team.
*** Bug 653857 has been marked as a duplicate of this bug. ***
Verified by provision a system and checking the harness files on system after installation. Now the harness files are placed in /mnt/testarea rather /tmp.
/distribution/kernelinstall task also passed with beaker-0.9.4-2.git.104.1433411.el6 + beah-0.6.41-1.el6eng (which contains the fix for this bug).
(In reply to comment #10) > /distribution/kernelinstall task also passed with > beaker-0.9.4-2.git.104.1433411.el6 + beah-0.6.41-1.el6eng (which contains > the fix for this bug). Could you verify it by trying rhts-reboot / normal reboot is working as we could see in bug 878411?
*** Bug 878411 has been marked as a duplicate of this bug. ***
(In reply to comment #11) > (In reply to comment #10) > > /distribution/kernelinstall task also passed with > > beaker-0.9.4-2.git.104.1433411.el6 + beah-0.6.41-1.el6eng (which contains > > the fix for this bug). > > Could you verify it by trying rhts-reboot / normal reboot is working as we > could see in bug 878411? Unfortunately, RHEL7 is not working well on my beaker instance, so I can't check this now. I tried /distribution/kernelinstall task with RHEL6 (comment 10), this task has rhts-reboot action include during the test, and it works. We can double check this with RHEL7 once the new build is deployed.
I realize this is already VERIFIED, but I wanted to throw something in the discussion on this. Why are any test files under /mnt? As a new user of beaker one of the first things that is confusing is noticing that nothing is actually mounted under /mnt for the tests. Why not put them somewhere else that doesn't imply a remote FS?
This has now been released
(In reply to comment #14) > I realize this is already VERIFIED, but I wanted to throw something in the > discussion on this. Why are any test files under /mnt? As a new user of > beaker one of the first things that is confusing is noticing that nothing is > actually mounted under /mnt for the tests. Why not put them somewhere else > that doesn't imply a remote FS? This is just my *guess*, but it could be the legacy of rhts (http://git.beaker-project.org/cgit/rhts/).