From Fedora Project Wiki

No edit summary
No edit summary
Line 10: Line 10:
* Terminal output is got by serial console
* Terminal output is got by serial console
* Guest installation logs are transfered by virtio
* Guest installation logs are transfered by virtio
== Understanding Failure ==
=== Boot Method ===
* installer fails to boot as a KVM guest
=== Install Source ===
* Dependency
* File Conflicts
=== Partation ===
* partation error with ks file
=== Kickstart Delivery ===
* installer cannot mount ks file
=== Serial Console ===
* installer cannot finish install with serial console
=== Logging ===
* installer cannot transfer anaconda logs by virtio
= 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:38, 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 Failure

Boot Method

  • installer fails to boot as a KVM guest

Install Source

  • Dependency
  • File Conflicts

Partation

  • partation error with ks file

Kickstart Delivery

  • installer cannot mount ks file

Serial Console

  • installer cannot finish install with serial console

Logging

  • installer cannot transfer anaconda logs by virtio

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.