Unfortunately I still haven't been able to test the whole
rats_install, because Beaker now has some congestion problems and it
fails to provision a machine very often on top of that. So hold on,
it might take a while until I have a bare metal machine available to
test rats_install fully.
I performed a successful test run on Fedora 15 x86_64 host. Unfortunately the successive
runs were not as successful. Comments:
1. ARCH is not filled in. Please fill it in.
https://fedoraproject.org/wiki/Writing_AutoQA_Tests#Architecture
2. SUMMARY is not filled in. Please fill it in.
https://fedoraproject.org/wiki/Writing_AutoQA_Tests#Summary
For example you can state which installation stage failed, or that all stages passed
3. There is only 20 minutes time limit for package installation. That is insanely low
limit. On the beaker machine I borrowed I managed to do just one installation properly
(packages installed in 19 minutes), all other attempts took longer and the installation
was aborted. I propose to raise the limit to 40 minutes.
4. I don't really understand why there is about 2-4 minutes delay between ./install.py
is run and between first anaconda test (.treeinfo check) is executed. It can be easily
seen from the logs. Can you investigate?
5. There seems to be some garbage characters in stage1.log and particularly in stage2.log.
That breaks our tests, because we grep for certain phrases and sometimes the phrases are
mixed with unreadable characters. What's the cause?
6. After the test run ends, all anaconda logs are transferred onto the server into
~autotest/results/test_id/machine/rats_install/results/anaconda/. Unfortunately the last
'anaconda' directory has permissions rwx------ and therefore it is not visible
from the web front-end (httpd user can't access it). We have to fix this somehow
(setting permissions when creating it is the easiest solution, but I wonder whether there
is something more elegant than that).
7. When debugging this test, I wanted to connect to the VM that was being installed to
have better grasp of what's going on. Unfortunately the serial port didn't work, I
couldn't log in over that (we use it probably for our purposes already). So I had to
add 'sshd' boot option to anaconda to be able to ssh into the machine. This could
be enabled by default, what do you think?
Apart from these issues it worked really well, great!
It's unfortunate that you're leaving now for a long holiday, hongqing. I can fix
some of these issues myself, the only serious problem I'm worried about is 5). That
will need a deeper investigation.