From Fedora Project Wiki
< QA
These are the current plans for automated testing of the installer. The specific goal is this: perform daily, basic, fully-automatic installations of Rawhide, and report the results to a public web page.
Hardware
- One server machine with enough disk space for a local mirror of rawhide
- Roughly 15G per arch. Ouch.
- One test machine per arch - i386, x86_64, and ppc.
- ppc is considered almost optional.
- KVM/QEMU/Xen could be used on the server machine to test in virtual guests.
- Must be PXE-capable
- Some form of power control
- This could be non-automated - "if the machine is dead, hit the power button".
Software
cobblerkoan- See http://fedorahosted.org/cobbler/ for more details
- Note that
- Rawhide sync script
- http://jkeating.fedorapeople.org/sync-rawhide.py is an example script
- Or you could just let cobbler handle it.
- logging client/server
- In progress.
Overall design
- Daily rawhide compose completes. We get signal.
- Rawhide gets synced up.
- Each client machine is instructed to run koan to install the new rawhide.
- This might happen via
- This might happen via
- A
%prescript in the kickstart runs the logging client- Watch the following log files:
/tmp: anaconda.log, syslog, ks-script.log, anacdump.txt, modprobe.conf/mnt/sysimage/root: install.log, upgrade.log
- Watch the following log files:
- If something fails during install
anacdump.txtappears, or no log data for 30min
- Use cobbler to change the PXE target to reinstall stable OS
- Use power control to restart the machine
- Close log task with status FAIL
- Otherwise:
%postscript in kickstart creates a service to run on firstboot- Send system startup logs (to be checked for errors)
- Send signal to logging server to close task with status OK
- Logging server checks over collected logs for errors
- avc errors in
/var/log/messages, FAILED in/var/log/boot.log, etc. - Change status to WARN if found.
- avc errors in