From Fedora Project Wiki
No edit summary |
|||
| Line 30: | Line 30: | ||
=== Logging === | === Logging === | ||
* installer cannot transfer anaconda logs by virtio | * installer cannot transfer anaconda logs by virtio | ||
= Usage= | |||
* The test result can be read directly from the test results, but errors do not block the installation should be read from the anaconda logs | |||
= Getting Help = | = Getting Help = | ||
If you still don't understand why your update failed the test, if you think there's something wrong in our test or its documentation or if you have any other suggestions, please [[AutoQA#Communicate|contact us]]. | If you still don't understand why your update failed the test, if you think there's something wrong in our test or its documentation or if you have any other suggestions, please [[AutoQA#Communicate|contact us]]. | ||
Revision as of 06:51, 7 March 2012
What Is Rats Install
rats_install test is a simple Python tool to test the daily Fedora tree compose.
How Does Rats Install Work
rats_install test the Fedora tree compose by installing the guest with virt-install and get the install logs by serial console and virtio.
- Test is triggered by compose watcher
- Event post-tree-comose
- virt-install is used to install guest from tree compose
- Terminal output is got by serial console
- Guest installation logs are transfered by virtio
Understanding Failures
Boot Method
- installer fails to boot as a KVM guest
- Dependency
Package Repository
- Unable to read metadata from package repositories
Package Set
- Dependency problems while resolving package list
- File conflicts during package install
- Improperly formatted comps.xml data
Partation
- Partation error with ks file
Bootloader
- Fail to install bootloaer
Kickstart Delivery
- installer cannot mount ks file
Serial Console
- installer cannot finish install with serial console
Logging
- installer cannot transfer anaconda logs by virtio
Usage
- The test result can be read directly from the test results, but errors do not block the installation should be read from the anaconda logs
Getting Help
If you still don't understand why your update failed the test, if you think there's something wrong in our test or its documentation or if you have any other suggestions, please contact us.